The answer is AWS SSO with an external identity provider. This is correct because AWS SSO allows you to invite external contractors without AWS accounts as external members via their email, granting them access to an AWS account through a centralized portal with temporary, limited-privilege credentials via permission sets, eliminating the need to create permanent IAM users. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of identity federation for temporary access, often appearing as a trap where candidates mistakenly choose IAM roles or Cognito—remember, IAM roles require existing AWS credentials to assume, and Cognito is designed for application users, not console access. A key memory tip: think of AWS SSO as the “guest pass” for contractors—no account needed, just an email invite and a time-limited portal login.
DOP-C02 Security and Compliance Practice Question
This DOP-C02 practice question tests your understanding of security and compliance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A startup wants to provide temporary, limited-privilege AWS access to external contractors who will assist with a project. The contractors do not have AWS accounts. The company wants to avoid creating IAM users for each contractor. They need a solution that allows contractors to log in to the AWS Management Console for a limited time. Which AWS service should the engineer use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use AWS SSO with an external identity provider, and grant access to an AWS account with a permission set.
AWS SSO can be used to grant external users access to AWS accounts via a portal, with temporary credentials. You can invite users as external members in AWS SSO, and they can log in with their own email and receive temporary credentials. IAM roles cannot be directly assumed without AWS credentials. Cognito is for app users. IAM users would require creating permanent users.
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 AWS SSO with an external identity provider, and grant access to an AWS account with a permission set.
Why this is correct
AWS SSO allows granting temporary console access to external users.
Related concept
Authentication checks who the user is.
✗
Create IAM users for each contractor and attach a policy with a condition to expire access after the project.
Why it's wrong here
Creates permanent IAM users, not recommended for external contractors.
✗
Use Amazon Cognito user pools to create temporary user accounts.
Why it's wrong here
Cognito is for application users, not AWS console access.
✗
Provide the contractors with the root user credentials of a separate AWS account.
Why it's wrong here
Root credentials should never be shared.
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 AWS SSO with an external identity provider, and grant access to an AWS account with a permission set. — AWS SSO can be used to grant external users access to AWS accounts via a portal, with temporary credentials. You can invite users as external members in AWS SSO, and they can log in with their own email and receive temporary credentials. IAM roles cannot be directly assumed without AWS credentials. Cognito is for app users. IAM users would require creating permanent users.
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.