The correct option is Integrated into every phase of the development lifecycle.

Integrated into every phase of the development lifecycle means that security activities are applied from requirements and architecture through design, implementation, testing, deployment, and operations. When security is applied continuously teams can perform threat modeling early, enforce secure design decisions, run static and dynamic analysis during implementation, and automate security tests in CI pipelines so that issues are detected and remediated sooner and at lower cost.

Integrated into every phase of the development lifecycle also supports compliance, secure configuration management, and effective incident response because security responsibilities and controls are defined for each stage rather than being left to a single phase or tool.

Monitored with Cloud Security Command Center is incorrect because that describes a runtime monitoring and asset discovery tool rather than a development lifecycle approach. Monitoring is valuable in production but it does not replace the need to build security into requirements, design, coding, and testing.

Added only after the design and deployment are complete is incorrect because adding security after deployment leads to expensive fixes and missed design flaws. Late integration increases risk and often requires major rework to address architectural vulnerabilities.

Addressed mainly during the implementation and coding phase is incorrect because focusing almost exclusively on coding misses opportunities to reduce risk earlier and later in the lifecycle. Requirements and design activities such as threat modeling and secure architecture reviews are necessary, and testing and operational controls are also required after implementation.

Full AWS Practitioner Certification Question