Courseiva
Design Solutions for Organizational ComplexityeasyMultiple ChoiceObjective-mapped

SAP-C02 Practice Question: Design Solutions for Organizational Complexity

A company uses a single AWS account for development and production workloads. To improve security and cost allocation, the company decides to separate environments into multiple accounts. What is the PRIMARY benefit of using multiple accounts?

⚠ Common exam trap

A common mix-up: candidates confuse the secondary benefit of cost savings (shared RIs) with the primary benefit of security isolation and centralized governance, which is the core reason for multi-account strategies in the SAP-C02 exam.

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

Enabling centralized security controls and consolidated billing.

Separating environments into multiple AWS accounts provides a strong security boundary (via AWS Organizations SCPs) and enables consolidated billing with cost allocation tags. This allows centralized security controls (e.g., guardrails, IAM policies) across accounts while aggregating usage for volume discounts, which is the primary benefit for improving security and cost allocation.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Reducing overall compute costs by sharing reserved instances across environments.

    Why it's wrong here

    Reserved instances can be shared across accounts, but this is not a primary benefit of separation.

  • Simplifying backup and disaster recovery procedures.

    Why it's wrong here

    Separating environments into multiple accounts does not inherently simplify backup or disaster recovery; these procedures depend on cross-region replication, backup policies, and organisational processes, not account count. The temptation arises because consolidated accounts can complicate recovery scopes, but the primary benefit of multi-account architecture is enforcing a hard security boundary and enabling granular cost allocation via AWS Organizations, not operational recovery tasks.

  • Decreasing network latency between development and production environments.

    Why it's wrong here

    Account separation does not affect network latency.

  • Enabling centralized security controls and consolidated billing.

    Why this is correct

    Multiple accounts allow SCPs and consolidated billing through AWS Organizations.

About these practice questions

Courseiva writes every SAP-C02 question from scratch — 1,660 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.