SAP-C02 Practice Question: Design Solutions for Organizational Complexity
A company has a multi-account AWS environment with over 500 accounts. The security team uses AWS Config to evaluate resource compliance across all accounts. They have set up an AWS Config aggregator in the security account to collect configuration snapshots from all member accounts. Recently, the team noticed that some member accounts are not showing up in the aggregator. The accounts are active and have AWS Config enabled. What should the security team do to troubleshoot this issue?
⚠ Common exam trap
Candidates often assume enabling AWS Config in member accounts is sufficient, overlooking the critical cross-account authorization step required by the aggregator to pull data from those accounts.
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
✓
Verify that the AWS Config aggregator in the security account has the correct authorization to assume a role in each member account.
AWS Config aggregators require cross-account authorization to collect configuration data from member accounts. Even if AWS Config is enabled in member accounts, the aggregator in the security account must have the correct IAM role permissions (via an IAM role in each member account) to assume and retrieve configuration snapshots. Without this authorization, the aggregator cannot access the member accounts' data, causing them to not appear.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ensure that the member accounts have enabled AWS Config in the same region as the aggregator.
Why it's wrong here
Config aggregators can collect from multiple regions, but the aggregator must be authorized per region; however, lack of authorization is more likely the cause.
- ✗
Check if the member accounts have exceeded the AWS Config resource limits.
Why it's wrong here
Resource limits would affect recording, not the ability to appear in an aggregator.
- ✗
Check if the AWS Config recorder in the member accounts is configured to record all resource types.
Why it's wrong here
The issue is likely not about resource types because some accounts are not appearing at all.
- ✓
Verify that the AWS Config aggregator in the security account has the correct authorization to assume a role in each member account.
Why this is correct
The aggregator needs cross-account IAM roles to retrieve data; if permissions are missing or incorrect, accounts won't appear.
Go deeper
Related to this question
About these practice questions
One of 1,660 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.