Matrix organizations do not usually minimize costs or simplify communication. They often increase communication complexity because employees may report to both functional and product, project, or geographic managers. This dual authority can create conflict, role ambiguity, slower decisions, and stress.
However, matrix structures can provide flexibility by allowing resources and expertise to move across projects or product lines. Option A is true because functional and product managers may disagree over priorities. Option B is true because dual command can increase workplace stress. Option C is true because flexibility is a major benefit of matrix design. Internal audit should assess whether accountability, approval authority, and conflict resolution are clearly defined in matrix structures. Therefore, Option D is false.

A bring-your-own-device environment increases exposure to malware because personal devices may not be configured, patched, monitored, or protected to the same standard as organization-owned devices. Employees may install unapproved applications, connect to insecure networks, delay updates, or mix personal and business use. Less efficiency and lower employee satisfaction are not typical BYOD benefits or core risks; BYOD often improves convenience and flexibility. Higher organizational device cost is also not the primary risk because the employee owns the device, although support and monitoring costs may increase. Internal auditors should review mobile device management, malware protection, encryption, acceptable use, patching, remote wipe, incident response, and user awareness. Therefore, Option D is correct.

Secure Sockets Layer, and its successor TLS, is used to protect communications between a client and server through encryption and authentication mechanisms. SSL/TLS helps verify the identity of the server through digital certificates and protects information sent between the client and server from interception or alteration.
It does not prevent phishing by itself, because a malicious site can still deceive users through look-alike domains or social engineering. It also does not prevent malware infections; anti-malware, patching, filtering, and user awareness controls are needed for that. Temporary session keys may be used within SSL/TLS, but the strongest answer given is that SSL supports authentication and secure transmission of information.
Therefore, Option A is correct.

Comprehensive and Detailed In-Depth Explanation:
Biometric authentication (e.g., fingerprint, retina scan) is the most difficult to revoke because it is linked to an individual's physical attributes, which cannot be changed like passwords or physical devices.
Option A (Traditional key lock) - Can be revoked by retrieving the key or changing the lock.
Option C (Card-key system) - Can be revoked by deactivating the card.
Option D (Proximity device) - Can be revoked by disabling the device.
Since biometric data is permanently tied to an individual, revoking access is complex, making Option B the correct answer.
Reference: IIA IT Security & Authentication Controls

Integration testing is a phase in the software development lifecycle (SDLC) where individual components or systems are combined and tested as a group to ensure they work together correctly.
Ensures Component Compatibility - Confirms that different software modules and hardware components function correctly when integrated.
Identifies Data Flow Issues - Ensures seamless communication between software systems, databases, and external applications.
Detects System-Wide Errors - Finds defects that unit testing (individual module testing) may miss.
Prepares for System Testing - Integration testing is conducted before full system testing to ensure subsystems work together as expected.
A). To verify that the application meets stated user requirements.
This refers to User Acceptance Testing (UAT), not integration testing.
B). To verify that standalone programs match code specifications.
This describes unit testing, where individual components are tested separately.
C). To verify that the application would work appropriately for the intended number of users.
This describes performance or load testing, which measures system behavior under high user load.
IIA's GTAG on IT Risks and Controls - Emphasizes the role of integration testing in ensuring secure and functional IT environments.
COBIT 2019 (Governance and Management of IT) - Recommends integration testing to reduce IT system failures.
ISO/IEC 25010 (Software Quality Model) - Lists integration testing as a key quality assurance step.
Why Option D is Correct?Why Not the Other Options?IIA References: