SCS-C03 Security Foundations and Governance Practice Question
An organization wants to centralize the management of Amazon GuardDuty across 50 AWS accounts. They want the security team to be able to view and manage findings for all accounts from a single dashboard. What is the recommended governance approach?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Designate a security account as the GuardDuty delegated administrator through the AWS Organizations management account.
AWS Organizations allows for delegated administration of security services. By designating a security account as the GuardDuty delegated administrator, the organization centralizes finding management. This allows the security team to enable GuardDuty in member accounts, view all findings, and manage suppression rules from one place, ensuring consistent threat detection governance across the entire enterprise.
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 an AWS CloudFormation StackSet to enable GuardDuty and an SNS topic in every account.
Why it's wrong here
While StackSets can automate the enablement of GuardDuty, they do not provide a centralized dashboard for managing findings. The security team would still need to access each account individually or manage a complex web of SNS notifications, which is not scalable or efficient for 50 accounts.
- ✓
Designate a security account as the GuardDuty delegated administrator through the AWS Organizations management account.
Why this is correct
This is the AWS-recommended approach for multi-account governance. The delegated administrator can manage GuardDuty for the entire organization, including auto-enrolling new accounts. This provides a single pane of glass for findings and centralizes the administration of threat detection without requiring manual cross-account configuration.
- ✗
Manually send invitations from the security account to each of the 49 member accounts to link them.
Why it's wrong here
While the invitation method works, it is the legacy approach and requires manual acceptance in each member account. Using the AWS Organizations integration is superior because it automates the linkage and allows for the 'auto-enable' feature, ensuring that new accounts are protected immediately upon creation.
- ✗
Configure an Amazon S3 bucket in each account to store findings and use Athena for centralized querying.
Why it's wrong here
Storing findings in S3 is useful for long-term archiving and custom analysis, but it does not provide the real-time management and response capabilities of the GuardDuty console. This approach adds significant complexity and latency compared to the native delegated administrator feature provided by AWS.
About these practice questions
This SCS-C03 question is part of Courseiva's 99-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SCS-C03 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-C03 exam.