The answer is to create IAM roles with the principle of least privilege, use service control policies (SCPs) to enforce permission boundaries, and delegate access across accounts using IAM roles. This combination is correct because SCPs act as a centralized guardrail in AWS Organizations, capping what member account principals can do, while least-privilege roles ensure that even within that boundary, permissions are minimal. Delegating via roles avoids sharing long-term credentials and aligns with the AWS recommended practice of cross-account access. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your understanding of how SCPs and IAM roles work together to enforce governance without breaking automation—a common trap is confusing SCPs with IAM policies, but remember SCPs never grant permissions, they only restrict. A memory tip: think of SCPs as the “ceiling” and IAM roles as the “floor”—you must set both to stay secure.
DOP-C02 Security and Compliance Practice Question
This DOP-C02 practice question tests your understanding of security and compliance. 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 of the following are best practices for managing IAM roles in AWS Organizations? (Choose three.)
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use service control policies (SCPs) to set permission boundaries.
Using IAM roles to delegate access across accounts is a best practice. Creating roles with least privilege and using service control policies (SCPs) to enforce permission boundaries are also best practices. Sharing root user credentials is never a best practice. Using a single IAM user across accounts is not recommended.
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.
✓
Use service control policies (SCPs) to set permission boundaries.
Why this is correct
SCPs help centrally control permissions for all accounts.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Authentication checks who the user is.
✗
Share the root user credentials of the master account with administrators.
Why it's wrong here
Root credentials should be protected and not shared.
✗
Use a single IAM user with full permissions across all accounts.
Why it's wrong here
This violates least privilege and security best practices.
✓
Use IAM roles to delegate access to users and services across accounts.
Why this is correct
Roles provide temporary credentials and are the recommended way to grant cross-account access.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Authentication checks who the user is.
✓
Create IAM roles with the principle of least privilege.
Why this is correct
Least privilege reduces risk.
Clue confirmation
The clue word "best" in the question point toward this answer.
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.
Security and Compliance — This question tests Security and Compliance — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use service control policies (SCPs) to set permission boundaries. — Using IAM roles to delegate access across accounts is a best practice. Creating roles with least privilege and using service control policies (SCPs) to enforce permission boundaries are also best practices. Sharing root user credentials is never a best practice. Using a single IAM user across accounts is not recommended.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.