Quick Answer
The answer is to enable MFA on the root user account and to avoid creating access keys for the root user. Enabling multi-factor authentication adds a critical second layer of security beyond the password, ensuring that even if credentials are compromised, an attacker cannot access the account without the physical MFA device. Not creating access keys is equally vital because access keys grant unrestricted programmatic access to all AWS resources and billing data, making them a prime target for attackers; eliminating them removes this high-risk vector entirely. On the AWS Certified Security Specialty SCS-C02 exam, this concept tests your understanding of the AWS shared responsibility model and the principle of least privilege, often appearing in scenario-based questions where a security engineer must harden the most privileged account. A common trap is assuming that a strong password alone is sufficient, but the exam emphasizes that the root user should only be used for tasks that require it, with MFA mandatory. Memory tip: think "Root MFA, no keys" — the root user must have MFA and must never have access keys.
This SCS-C02 practice question tests your understanding of management and security governance. 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 TWO actions should a security engineer take to protect root user credentials? (Select TWO.)
Use the root user only for billing
Why wrong: Root user should not be used for daily tasks.
Share the root user credentials with the security team
Why wrong: Credentials should not be shared.
Do not create access keys for the root user
Access keys increase risk.
Enable MFA on the root user account
MFA adds a second factor.
Delete the root user account
Why wrong: Root user cannot be deleted.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Do not create access keys for the root user
Option C is correct because AWS strongly recommends that you do not create access keys for the root user. Access keys provide programmatic access to the AWS API, and if compromised, an attacker would have unrestricted access to all AWS resources and billing information. By not creating access keys, you eliminate this high-risk attack vector.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Use the root user only for billing
Why it's wrong here
Root user should not be used for daily tasks.
Share the root user credentials with the security team
Why it's wrong here
Credentials should not be shared.
Do not create access keys for the root user
Why this is correct
Access keys increase risk.
Related concept
Read the scenario before looking for a memorised answer.
Enable MFA on the root user account
Why this is correct
MFA adds a second factor.
Related concept
Read the scenario before looking for a memorised answer.
Delete the root user account
Why it's wrong here
Root user cannot be deleted.
Common exam traps
The trap here is that candidates often think the root user can be deleted or that using it only for billing is acceptable, but AWS explicitly prohibits deleting the root user and recommends using IAM users with billing permissions instead.
Detailed technical explanation
The root user has unrestricted access to all AWS services and resources, including the ability to change account settings, close the account, and access billing data. AWS enforces that the root user cannot be deleted because it is the account owner; instead, you should secure it with a strong password and MFA, and avoid using it for daily operations. In a real-world scenario, if an organization creates access keys for the root user and stores them in a CI/CD pipeline, a single leak could lead to a full account takeover.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Management and Security Governance — study guide chapter
Learn the concepts, then practise the questions
Management and Security Governance practice questions
Targeted practice on this topic area only
All SCS-C02 questions
1,738 questions across all exam domains
AWS Certified Security Specialty SCS-C02 study guide
Full concept coverage aligned to exam objectives
SCS-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SCS-C02 questions linked to Threat Detection and Incident Response.
Practise SCS-C02 questions linked to Security Logging and Monitoring.
Practise SCS-C02 questions linked to Identity and Access Management.
Practise SCS-C02 questions linked to Management and Security Governance.
Practise SCS-C02 questions linked to Infrastructure Security.
Practise SCS-C02 questions linked to Data Protection.
Practise SCS-C02 questions linked to SCS-C02 fundamentals.
Practise SCS-C02 questions linked to SCS-C02 scenario.
Practise SCS-C02 questions linked to SCS-C02 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Management and Security Governance — This question tests Management and Security Governance — Read the scenario before looking for a memorised answer..
The correct answer is: Do not create access keys for the root user — Option C is correct because AWS strongly recommends that you do not create access keys for the root user. Access keys provide programmatic access to the AWS API, and if compromised, an attacker would have unrestricted access to all AWS resources and billing information. By not creating access keys, you eliminate this high-risk attack vector.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
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 →
Keep practising
Last reviewed: Jun 24, 2026
This SCS-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 SCS-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.