The correct option is Implement early planning with cross team collaboration and automation.

This option is correct because planning early brings security into design and requirements so teams can build controls rather than bolt them on later. Cross team collaboration between security, engineering, and compliance ensures evidence needs are identified early and prevents last minute surprises that delay authorization.

Automation is a key part of the correct approach because it enables repeatable evidence collection and continuous monitoring. Automated pipelines and tooling reduce manual effort and errors and they make assessments faster and more reliable as systems evolve.

Delay security involvement until late stages is wrong because waiting until late means controls are often missing or costly to retrofit and that increases the chance of rework and authorization delays.

Security Command Center is wrong because naming a single tool does not address the broader need for early planning, team collaboration, and automation across the organization. A product alone will not guarantee authorization success.

Rely on manual evidence gathering and paper based controls is wrong because manual and paper based processes are slow and error prone. They do not scale for continuous monitoring and they make frequent reassessments expensive and risky.

Full AWS Practitioner Certification Question