DJames617 CLF-C02 / Domain 3 / 34%
Cloud Technology and Services
Deployment, global infrastructure, compute, database, network, storage, AI/ML, analytics, and service categories.
Official Task Statements
| Task | What to prove |
|---|---|
| CLF-3.1 | Define methods of deploying and operating in the AWS Cloud. |
| CLF-3.2 | Define the AWS global infrastructure. |
| CLF-3.3 | Identify AWS compute services. |
| CLF-3.4 | Identify AWS database services. |
| CLF-3.5 | Identify AWS network services. |
| CLF-3.6 | Identify AWS storage services. |
| CLF-3.7 | Identify AWS artificial intelligence, machine learning, and analytics services. |
| CLF-3.8 | Identify services from other in-scope AWS service categories. |
Concepts You Need to Understand
- Compute, storage, databases, networking, global infrastructure, deployment methods, AI/ML, analytics, integration, and management tools.
AWS services involved
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
- RDS
- DynamoDB
- VPC
- CloudFront
- Route 53
- CloudWatch
Important configurations
- Know public, private, and hybrid access patterns conceptually.
- Match service families to workloads before memorizing products.
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
- Choosing a service by name recognition instead of workload fit.
- Assuming every AWS service is global.
Example Architecture
Hands-On Activity
Use the AWS console service search and inspect service categories without creating resources.
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-3.1 - Define methods of deploying and operating in the AWS Cloud.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Define methods of deploying and operating in the AWS Cloud.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.1 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.2 - Define the AWS global infrastructure.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Define the AWS global infrastructure.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.2 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.3 - Identify AWS compute services.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify AWS compute services.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.3 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.4 - Identify AWS database services.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify AWS database services.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.4 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.5 - Identify AWS network services.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify AWS network services.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.5 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.6 - Identify AWS storage services.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify AWS storage services.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.6 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.7 - Identify AWS artificial intelligence, machine learning, and analytics services.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify AWS artificial intelligence, machine learning, and analytics services.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.7 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.
CLF-3.8 - Identify services from other in-scope AWS service categories.
Read this task as a decision problem: identify the workload requirement, the control or service family involved, and the tradeoff AWS is testing. The validated local corpus connects this objective to 6 official AWS sources and identifies these study anchors:
- Identify services from other in-scope AWS service categories.
- Cloud Technology and Services
- EC2
- Lambda
- ECS
- S3
- EBS
- EFS
How to apply the material
- 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.
Explain before memorizing
Know this distinction: explain why the selected approach fits the requirement, what it does not provide, and which customer-managed control remains. Then test the explanation against a changed constraint: a different failure boundary, traffic pattern, data sensitivity, latency target, or operating-cost limit.
Exam habit: when two answers seem technically possible, prefer the one that matches the stated outcome and shared-responsibility boundary. Do not assume that a managed service removes identity, data-protection, configuration, monitoring, recovery, or cost responsibilities.
Mastery check before Arcade practice
- I can define the central terms and explain what problem the objective is solving.
- I can select the best answer from a realistic scenario without relying on a product name alone.
- I can explain why the closest distractor is wrong when one requirement changes.
- I can identify the AWS-managed boundary and the customer-managed control that remains.
- I can predict the main availability, security, scaling, operations, or cost consequence of the choice.
Use the Arcade after you can explain all five checks aloud or in writing. If an answer is correct only because it looks familiar, return to the source anchors and compare the service purpose, constraints, and tradeoffs again.
Practice CLF-3.8 style questions in this domain
Official AWS references for this objective
- AWS docs / aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html
- AWS docs / wellarchitected/latest/framework/welcome.html
- AWS docs / IAM/latest/UserGuide/introduction.html
- AWS docs / organizations/latest/userguide/orgs_introduction.html
- AWS docs / cost-management/latest/userguide/budgets-managing-costs.html
Sources are from the validated local corpus; retrieved 2026-08-14. Retrieval metadata and hashes are retained in the corpus manifest.