SCS-C02 Security Logging and Monitoring Practice Question
A security engineer is using Amazon GuardDuty in a multi-account environment managed by AWS Organizations. The engineer wants to ensure that GuardDuty findings from all member accounts are centrally visible and that new accounts are automatically enrolled. What should the engineer do?
⚠ Common exam trap
The trap here is assuming that Security Hub or EventBridge can manage GuardDuty enrollment, when only the delegated administrator feature provides automatic enablement and central management.
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 delegated administrator for GuardDuty in the organization and enable GuardDuty for all accounts.
Designating a delegated administrator for GuardDuty in AWS Organizations allows centralized management, automatic enrollment of new accounts, and aggregation of findings. This is the most efficient and recommended method for multi-account GuardDuty deployment. Other options require manual configuration and do not provide automatic enrollment or central visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create an Amazon EventBridge rule in each account that forwards GuardDuty findings to a central event bus.
Why it's wrong here
Forwarding findings via EventBridge requires manual setup in each account and does not enable GuardDuty or automatically enroll new accounts. It also adds complexity and does not provide a centralized view of findings in the GuardDuty console. This solution addresses only the forwarding of findings, not the management of GuardDuty across accounts.
- ✗
Enable GuardDuty in each member account and configure each account to publish findings to a central SNS topic.
Why it's wrong here
Enabling GuardDuty individually in each account and manually configuring SNS publishing is operationally intensive and does not provide automatic enrollment for new accounts. It also does not aggregate findings in a single console. This approach lacks the centralized management and automation that Organizations integration provides.
- ✓
Designate a delegated administrator for GuardDuty in the organization and enable GuardDuty for all accounts.
Why this is correct
Designating a delegated administrator allows a member account to manage GuardDuty for the entire organization. The administrator can enable GuardDuty for all existing and new accounts automatically. Findings from all accounts are aggregated in the delegated administrator account, providing central visibility. This is the recommended approach for multi-account GuardDuty management.
- ✗
Use AWS Security Hub to aggregate GuardDuty findings from all accounts.
Why it's wrong here
Security Hub can aggregate findings from GuardDuty and other services, but it does not automatically enroll new accounts in GuardDuty. The requirement is to ensure GuardDuty is enabled for all accounts and new accounts are automatically enrolled. Security Hub alone does not manage GuardDuty enablement across the organization.
Go deeper
Related to this question
About these practice questions
This SCS-C02 question is part of Courseiva's 1,205-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-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.