SAP-C02 Practice Question: Design Solutions for Organizational Complexity
A company has a multi-account environment with a central security account. They want to use AWS Security Hub to aggregate findings from all accounts. What is the correct setup?
⚠ Common exam trap
Test-takers frequently confuse Security Hub's multi-account model with other aggregation services like AWS Config aggregator or CloudWatch cross-account dashboards, assuming any cross-account aggregation tool can consolidate Security Hub findings, when in fact Security Hub requires its own dedicated multi-account feature.
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
✓
Enable Security Hub in the central account and invite member accounts to enable Security Hub.
AWS Security Hub uses a multi-account architecture where a central administrator account invites member accounts to enable Security Hub. This allows the administrator account to aggregate findings, insights, and compliance scores from all member accounts into a single view, enabling centralized security monitoring without additional forwarding infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set up Amazon EventBridge to forward findings from each account to the central account.
Why it's wrong here
Security Hub aggregation is configured by designating an administrator account and inviting member accounts, which then send findings natively. EventBridge forwarding duplicates findings manually and loses the central aggregation model. EventBridge is intended for routing events to targets such as Lambda or SNS for automated remediation, not for Security Hub cross-account consolidation.
- ✗
Use Amazon CloudWatch cross-account dashboards to view findings.
Why it's wrong here
CloudWatch dashboards visualise metrics and logs, not Security Hub findings, and provide no cross-account finding aggregation or ASFF normalisation. CloudWatch is the right tool for operational metric dashboards, whereas Security Hub aggregation requires a designated administrator account with member accounts associated to it.
- ✗
Enable AWS Config aggregator in the central account.
Why it's wrong here
AWS Config aggregators collect configuration item and compliance data, not Security Hub findings, so they cannot centralise ASFF findings. Config aggregation is correct when you need a multi-account view of resource configuration and conformance packs, not security finding consolidation.
- ✓
Enable Security Hub in the central account and invite member accounts to enable Security Hub.
Why this is correct
Security Hub aggregation requires enabling it in the central account as the administrator, then inviting member accounts to enable Security Hub and accept the invitation. Findings from all accounts then flow into the central account, satisfying the multi-account aggregation requirement.
Go deeper
Related to this question
About these practice questions
One of 984 original SAP-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-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 SAP-C02 exam.