1.0 SDLC Automation DOP-C02 Practice Quiz

• A. A staged CI/CD pipeline with source, build, test, approval, and deploy actions
• B. A single manual deployment script that operators run from a workstation
• C. A production deployment that starts before build artifacts are created
• D. A repository branch naming policy with no automated stages

A staged pipeline maps SDLC phases to auditable automation, making each promotion decision traceable before production deployment. This is the correct answer.

• A. Automate build, test, and deployment feedback loops around version-controlled changes
• B. Delay all tests until after production deployment
• C. Use production servers as the primary build environment
• D. Remove source control so developers can patch faster

DevOps-oriented SDLC automation shortens feedback loops and makes version-controlled changes the unit of release. This is the correct answer.

• A. Manual integration only at the end of each quarter
• B. Continuous integration with controlled continuous delivery promotion
• C. Continuous deployment directly to production with no validation gates
• D. Ad hoc artifact uploads that bypass version control

Continuous integration gives early build and test feedback, while continuous delivery keeps production promotion controlled by later validation or approval. This is the correct answer.

• A. Build a new artifact independently inside every target account
• B. A central pipeline that assumes cross-account deployment roles and promotes the same artifact
• C. Share long-term access keys from production with the build account
• D. Deploy only from developer laptops into each account

A central pipeline with cross-account roles preserves artifact identity while separating duties across target accounts. This is the correct answer.

• A. Assume one Regional artifact bucket is automatically available to all pipeline actions
• B. Use Region-aware actions, artifact stores, and deployment roles for each target Region
• C. Use a single Availability Zone as the deployment boundary
• D. Rename the production branch once per Region

Multi-Region pipelines need artifact availability and permissions aligned to the Region where each action runs. This is the correct answer.

• A. Overwrite the same artifact name for every build
• B. Edit the Lambda function code manually after pipeline deployment
• C. Trace each deployment artifact to an immutable source revision and build run
• D. Use one shared branch for all hotfixes without tagging releases

Linking source revision, build execution, artifact, and deployment target provides release traceability across the SDLC. This is the correct answer.

• A. Use the root user for every environment deployment
• B. Use the same unrestricted role for build, test, and production deployment
• C. Use one pipeline with separate stages and scoped deployment roles for each environment
• D. Deploy directly from feature branches to production without gates

A single-account pipeline can still separate environments through stages, approvals, and least-privilege deployment roles. This is the correct answer.

• A. Long-lived branches that merge only after months of development
• B. Production deployment on every commit with no environment separation
• C. Manual copy of source files between environments
• D. Automated validation on frequent commits with promotion gates for protected environments

Frequent integration reduces merge risk, and promotion gates prevent unvalidated changes from reaching protected environments. This is the correct answer.