5 Comprehensive Practice and Review
Review the four AWS Certified Cloud Practitioner exam domains through core cloud concepts, security responsibilities, service distinctions, infrastructure design, and cost-management options.
Exam domains and weighting
The scored AWS Certified Cloud Practitioner exam content is weighted across four domains: Cloud Concepts, ; Security and Compliance, ; Cloud Technology and Services, ; and Billing, Pricing, and Support, . These weights describe the current exam guide’s scored content, not a prediction of the exact mix of questions on an exam.
Cloud concepts and architecture
Cloud benefits and architecture concepts are often tested by distinguishing similar ideas. means adjusting resources as demand changes: a retailer might add resources during seasonal promotions and reduce them afterward. High availability instead concerns maintaining service availability; it does not mean scaling capacity up and down.
is the minimal-change migration approach. It moves an application with few or no changes, sometimes called “lift and shift.” Refactoring changes the application to use cloud-native capabilities. In the practice scenario where a company wants to move quickly with minimal changes and consider redesign later, is the suitable approach; retiring the application or retaining it on premises does not meet that stated goal.
The has six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Reliability and security are pillars. Global reach and licensing flexibility may matter in cloud decisions, but they are not pillars; fixed capacity is neither a pillar nor a cloud design goal.
Security responsibilities and tools
AWS is responsible for security of the cloud, while customers are responsible for security in the cloud. The exact division of duties depends on the service. With Amazon EC2, the customer manages the guest operating system, including its configuration and patches, while AWS manages the underlying cloud infrastructure. Managed services reduce some customer operational tasks, but they do not eliminate customer security responsibilities.
means granting only the access needed for a task. For temporary access to an AWS service, grant only the required permissions, preferably through an appropriate role. Avoid using the root user for routine work, attaching broad administrator permissions permanently, or sharing another employee’s access key. Compliance reports do not substitute for securing a customer’s own resources.
Know the distinct purposes of the security-related services and tools: records account activity and API events, helping establish who performed an action and when. Amazon CloudWatch is primarily for monitoring metrics, logs, and alarms. Amazon GuardDuty detects potential threats, AWS Inspector is among the security services to know, AWS Security Hub is also part of the review set, and AWS Artifact provides access to AWS compliance reports and agreements. CloudTrail is the right choice when the need is to record account activity; compliance reports from Artifact are not a replacement for securing resources.
AWS services by function
Match services to the kind of resource or function needed. provides object storage, making it suitable for durable storage of images and documents retrieved over the internet. Amazon EBS provides block storage commonly used with EC2. Amazon EFS is file storage. is a managed relational database service, while Amazon DynamoDB is a managed NoSQL database. Amazon VPC provides a virtual networking environment, and Amazon CloudFront is a content delivery network.
For compute, Amazon EC2 provides virtual servers. runs code in response to events without requiring the customer to provision or manage servers. In the practice scenario asking for event-driven code execution without server management, Lambda is the fit. AWS Direct Connect instead provides a dedicated network connection to AWS.
A managed relational database use case points to , not DynamoDB, EFS, or CloudFront. Durable object storage points to , not EBS, RDS, or VPC. These distinctions help match each business need to a service’s purpose.
Regions and availability
A Region contains multiple , and a Region is not the same thing as an Availability Zone. are separate locations within a Region. For high availability within one Region, deploying across multiple can help an application withstand an Availability Zone failure.
Do not assume that resources in one Availability Zone are automatically replicated to every Region, or that AWS automatically replicates every regional resource to other Regions. Cross-Region replication is not automatic for every resource. The practice scenario’s accurate statements are that are separate locations within a Region and that deploying across multiple Zones can help an application withstand a Zone failure.
Billing, pricing, and cost tools
Choose a cost-management option based on whether the task is analyzing past costs, tracking thresholds, estimating future plans, or obtaining a pricing commitment. helps analyze historical AWS costs and usage, identify trends, and view forecasts. AWS Budgets can alert when actual or forecast costs reach defined thresholds. The AWS Pricing Calculator estimates the costs of planned usage; it does not apply a usage commitment.
On-Demand avoids a long-term usage commitment. offer reduced prices in exchange for a commitment to a consistent amount of eligible compute usage over a term. Some Reserved Instance options also involve commitments. Spot Instances use spare capacity and may be interrupted; Spot alone is not the option for steady, predictable compute use with a commitment.
A low per-unit price does not guarantee a low total bill if usage is high. In the practice scenarios, use Cost Explorer to examine historical spending, trends, and forecasts, and use when steady, predictable eligible compute usage and a commitment fit the need.
Review approach and common misconceptions
Use missed questions to identify concepts that need review, rather than memorizing only answer letters. Revisit the relevant domain and distinctions, then retry without looking at the explanations. Prioritize weaker areas while giving extra study time to the larger-weighted Security and Technology domains.
Useful distinctions to revisit include versus high availability; versus refactoring; customer versus AWS responsibilities; object versus block storage; Regions versus ; and cost analysis versus cost estimation. Check current domain scope and service references against the official exam guide.