DJames617 CLF-C02 / Domain 2 / 30%
Security and Compliance
Shared responsibility, security, governance, compliance, access management, and security resources.
Official Task Statements
| Task | What to prove |
|---|---|
| CLF-2.1 | Understand the AWS shared responsibility model. |
| CLF-2.2 | Understand AWS Cloud security, governance, and compliance concepts. |
| CLF-2.3 | Identify AWS access management capabilities. |
| CLF-2.4 | Identify components and resources for security. |
Concepts You Need to Understand
- Shared responsibility, IAM fundamentals, root user protection, governance, compliance, encryption, security services, and audit evidence.
AWS services involved
- IAM
- IAM Identity Center
- AWS Organizations
- AWS KMS
- CloudTrail
- AWS Config
- GuardDuty
- Security Hub
Important configurations
- MFA on privileged users.
- Least-privilege policies.
- Organization-level trails and guardrails.
Exam Decision Patterns
Least operational overhead
Prefer managed and serverless services when they satisfy the requirement. Exceptions appear when the scenario needs host control, unsupported runtimes, specialized network behavior, or exact migration compatibility.
Highly available
Identify the failure boundary. One instance is not HA. Multiple instances in one AZ help capacity but not AZ failure. Multi-AZ handles regional AZ faults. Multi-Region handles regional events but adds complexity and cost.
Durable
Durability is about preserving data. Use replication, versioning, backups, point-in-time recovery, and tested restore plans. A durable backup does not guarantee a low RTO.
Decouple the application
Use SQS for buffering work, SNS for fanout, EventBridge for event routing, and Step Functions for visible workflow state. Add retries, DLQs, and idempotent consumers.
Least privilege
Prefer roles and temporary credentials, scope actions/resources/conditions, watch explicit denies, and remember that resource policies may also be required.
Common Mistakes
- Assuming AWS secures customer data automatically.
- Using root credentials for normal administration.
Example Architecture
Hands-On Activity
Open IAM Access Analyzer policy validation and inspect findings for a sample policy.
For an AWS-account lab, use one of the linked mini labs and keep cleanup steps visible before you start.
Task-by-Task Study Notes
CLF-2.1 - Understand the AWS shared responsibility model.
This task statement is asking whether you can turn a scenario into a decision. Start by identifying the workload requirement, the control or service family involved, and the tradeoff AWS is testing in this domain.
- Translate the wording into requirements: security, operations, cost, availability, latency, governance, or data behavior.
- Choose the service or configuration that directly satisfies those requirements with the least unnecessary complexity.
- Reject options that are technically possible but miss the domain goal or increase risk without a requirement.
CLF-2.2 - Understand AWS Cloud security, governance, and compliance concepts.
This task statement is asking whether you can turn a scenario into a decision. Start by identifying the workload requirement, the control or service family involved, and the tradeoff AWS is testing in this domain.
- Translate the wording into requirements: security, operations, cost, availability, latency, governance, or data behavior.
- Choose the service or configuration that directly satisfies those requirements with the least unnecessary complexity.
- Reject options that are technically possible but miss the domain goal or increase risk without a requirement.
CLF-2.3 - Identify AWS access management capabilities.
This task statement is asking whether you can turn a scenario into a decision. Start by identifying the workload requirement, the control or service family involved, and the tradeoff AWS is testing in this domain.
- Translate the wording into requirements: security, operations, cost, availability, latency, governance, or data behavior.
- Choose the service or configuration that directly satisfies those requirements with the least unnecessary complexity.
- Reject options that are technically possible but miss the domain goal or increase risk without a requirement.
CLF-2.4 - Identify components and resources for security.
This task statement is asking whether you can turn a scenario into a decision. Start by identifying the workload requirement, the control or service family involved, and the tradeoff AWS is testing in this domain.
- Translate the wording into requirements: security, operations, cost, availability, latency, governance, or data behavior.
- Choose the service or configuration that directly satisfies those requirements with the least unnecessary complexity.
- Reject options that are technically possible but miss the domain goal or increase risk without a requirement.
Review Checklist
Sources and Review Metadata
This independent training application is not affiliated with or endorsed by Amazon Web Services. AWS, Amazon Web Services, and AWS certification names are trademarks of Amazon.com, Inc. or its affiliates.