The answer is encrypting artifacts in transit and at rest using AWS KMS, scanning for vulnerabilities in dependencies and code, and applying least privilege IAM roles. These three practices form the core of CI/CD pipeline security best practices because encryption protects sensitive data from exposure during build and deployment stages, vulnerability scanning prevents insecure code from reaching production, and least privilege IAM roles limit the blast radius if credentials are compromised. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your ability to distinguish automated security controls from insecure shortcuts—a common trap is choosing “store credentials in the source repository” or relying solely on manual approval, both of which violate the principle of defense in depth. Remember the mnemonic “ELS” for Encrypt, scan for vulnerabilities, and enforce Least privilege to lock down your pipeline.
DOP-C02 SDLC Automation Practice Question
This DOP-C02 practice question tests your understanding of sdlc automation. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE practices help ensure the security of a CI/CD pipeline that deploys to production? (Choose three.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Integrate static code analysis and vulnerability scanning into the pipeline.
A: Encryption of artifacts in transit and at rest protects sensitive data. B: Scanning for vulnerabilities in dependencies and code helps prevent insecure deployments. D: Using least privilege IAM roles minimizes risk. C is wrong because storing credentials in the source repository is insecure. E is wrong because manual approval alone does not ensure security; automated checks are also needed.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Integrate static code analysis and vulnerability scanning into the pipeline.
Why this is correct
Automated scanning catches security issues early.
Related concept
Authentication checks who the user is.
✗
Require manual approval for all deployments to production.
Why it's wrong here
Manual approval is a gate but not a security practice per se; it does not prevent insecure code.
✓
Use IAM roles with least privilege for pipeline actions.
Why this is correct
Least privilege reduces the blast radius of a compromise.
Related concept
Authentication checks who the user is.
✗
Store deployment credentials in the source repository for traceability.
Why it's wrong here
Credentials should not be stored in source; use AWS Secrets Manager or Parameter Store.
✓
Encrypt artifacts in transit and at rest using AWS KMS.
Why this is correct
Encryption protects data integrity and confidentiality.
Related concept
Authentication checks who the user is.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DOP-C02 questions on access control and AAA configuration.
SDLC Automation — This question tests SDLC Automation — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Integrate static code analysis and vulnerability scanning into the pipeline. — A: Encryption of artifacts in transit and at rest protects sensitive data. B: Scanning for vulnerabilities in dependencies and code helps prevent insecure deployments. D: Using least privilege IAM roles minimizes risk. C is wrong because storing credentials in the source repository is insecure. E is wrong because manual approval alone does not ensure security; automated checks are also needed.
What should I do if I get this DOP-C02 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DOP-C02 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DOP-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.