The correct three actions are applying a stack policy to prevent updates to sensitive resources, using IAM policies to restrict who can create or modify stacks, and assigning a service role to enforce least privilege during stack operations. A stack policy acts as a resource-level guardrail, explicitly denying updates to critical components like databases or security groups even if the user has broad IAM permissions, while IAM policies control user-level access and service roles delegate temporary permissions to CloudFormation itself. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your ability to layer defense-in-depth for stack management, often trapping candidates who confuse stack policies with deletion policies or invent properties like StackSetPolicy. Remember the three pillars: IAM for who, stack policy for what, and service role for how. A useful memory tip is "Who, What, How" — IAM controls who acts, stack policy controls what can be changed, and the service role controls how CloudFormation performs the action.
DOP-C02 Configuration Management and IaC Practice Question
This DOP-C02 practice question tests your understanding of configuration management and iac. 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 actions should a DevOps engineer take to ensure that AWS CloudFormation stacks are securely managed? (Choose three.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a service role with least privilege when creating the stack.
Option A is correct because IAM policies can restrict who can create/modify stacks. Option C is correct because stack policies protect critical resources during updates. Option D is correct because using service roles follows least privilege. Option B is wrong because there is no 'StackSetPolicy' property. Option E is wrong because deletion policies are for individual resources, not the whole stack.
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.
✗
Set a DeletionPolicy on the stack to retain resources when the stack is deleted.
Why it's wrong here
DeletionPolicy applies to individual resources, not the stack itself.
✓
Use a service role with least privilege when creating the stack.
Why this is correct
Service roles allow CloudFormation to perform actions on behalf of the user.
Related concept
Authentication checks who the user is.
✓
Use IAM policies to restrict CloudFormation actions to specific users and roles.
Why this is correct
IAM policies control access to CloudFormation operations.
Related concept
Authentication checks who the user is.
✗
Define a StackSetPolicy to control permissions across accounts.
Why it's wrong here
StackSetPolicy is not a valid AWS resource.
✓
Apply a stack policy to prevent updates to sensitive resources during stack updates.
Why this is correct
Stack policies protect resources from unintended updates.
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.
Configuration Management and IaC — This question tests Configuration Management and IaC — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use a service role with least privilege when creating the stack. — Option A is correct because IAM policies can restrict who can create/modify stacks. Option C is correct because stack policies protect critical resources during updates. Option D is correct because using service roles follows least privilege. Option B is wrong because there is no 'StackSetPolicy' property. Option E is wrong because deletion policies are for individual resources, not the whole stack.
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.