The correct answer is Perform security assessments of both the individual components and the integration points.

This approach is correct because independent modules can contain implementation flaws and insecure configurations while the connections between them can introduce new weaknesses. A combined assessment finds issues inside each component and also discovers problems that only appear when components interact.

Component level testing validates secure configurations, dependency and library vulnerabilities, authentication and authorization within each module, and patching. Integration testing evaluates APIs, communication channels, data flows across trust boundaries, error handling, and how security controls behave end to end under realistic conditions.

Focus only on the interfaces between systems and disregard the security of each module is incorrect because ignoring module level flaws leaves obvious vulnerabilities untested and exploitable even if the interfaces seem secure.

Rely exclusively on Cloud Security Command Center to declare the solution secure is incorrect because tooling provides visibility and alerts but it cannot replace design review, code review, configuration checks, and active testing such as penetration testing and integration validation.

Assess only the individual components and skip testing how they work together is incorrect because many vulnerabilities arise from interactions and emergent behavior that component tests do not reveal, so skipping integration testing leaves the overall solution at risk.

Full AWS Practitioner Certification Question