Management and Governance
RecognitionAWS Control Tower
Multi-account governance context; no direct skill names it.
Key points
- Control Tower is multi-account governance context and receives recognition depth unless a task names its governed environment.
Best-known use cases
- D1.1, D1.2, and D3.1: operate a named governed account environment without replacing task-specific IAM, Organizations, or Config controls.
What candidates often confuse it with
- Control Tower supplies a governed multi-account context; Organizations, SCPs, and Config remain the underlying task-specific boundaries.
Key takeaway
Recognize Control Tower as context, then answer from the exact guardrail, account, identity, or compliance requirement.
Related services
- AWS Auto Scaling
- AWS CDK
- AWS CloudFormation
Relevant exam tasks
- D1.1 — Task 1.1: Implement metrics, alarms, and filters by using AWS monitoring and logging services.
- 1.1.1 — Use AWS services (for example, Amazon CloudWatch, AWS CloudTrail, Amazon Managed Service for Prometheus) to configure monitoring and logging for workloads (for example, serverless, compute, AI).
- D1.2 — Task 1.2: Identify and remediate issues by using monitoring and availability metrics.
- 1.2.1 — Analyze performance metrics and automate remediation strategies by using AWS services and functionality (for example, CloudWatch, Lambda, AWS Systems Manager, CloudTrail, Kiro, AWS DevOps Agent).
- D3.1 — Task 3.1: Provision and maintain cloud resources.
- 3.1.1 — Create and manage AMIs and container images (for example, EC2 Image Builder).