Cloud Practitioner
Entry-level AWS certification validating foundational cloud knowledge.
Getting Started: Your Cloud Practitioner Journey
Free knowledge base
AWS Certified Cloud Practitioner (CLF-C02) — key terms, tricks & tips
Everything from the course in one searchable place: 245 entries. Use it to review before a practice test or look up a word you forgot.
245 results
Domain
A section of the exam covering a specific topic area.
Getting Started: Your Cloud Practitioner Journey
Scaled Score
A transformed raw score, typically ranging from 100-1000 for AWS exams.
Getting Started: Your Cloud Practitioner Journey
Multiple-Choice
A question with one correct answer from several options.
Getting Started: Your Cloud Practitioner Journey
Multiple-Response
A question requiring selection of two or more correct answers.
Getting Started: Your Cloud Practitioner Journey
Pearson VUE
One of the authorized testing providers for AWS certifications.
Getting Started: Your Cloud Practitioner Journey
PSI
Another authorized testing provider for AWS certifications.
Getting Started: Your Cloud Practitioner Journey
Free Tier
AWS offering free, limited usage of many services for new accounts.
Getting Started: Your Cloud Practitioner Journey
Understanding the AWS Certified Cloud Practitioner Exam
To remember the exam domains: C-S-T-B (Cloud, Security, Technology, Billing). Think 'Can't Stop Thinking Big' to remember the order of importance for study.
Getting Started: Your Cloud Practitioner Journey
Understanding the AWS Certified Cloud Practitioner Exam
The exam specifically asks about the AWS Shared Responsibility Model. Memorize that AWS is responsible for 'security OF the cloud' (hardware, software, networking, facilities) and the customer is responsible for 'security IN the cloud' (customer data, operating systems, network configuration, client-side encryption).
Getting Started: Your Cloud Practitioner Journey
Understanding the AWS Certified Cloud Practitioner Exam
Underestimating the importance of the 'Billing, Pricing, and Support' domain; it's a smaller percentage but often overlooked.
Getting Started: Your Cloud Practitioner Journey
Understanding the AWS Certified Cloud Practitioner Exam
Only memorizing facts without understanding the underlying concepts or 'why' a service is used.
Getting Started: Your Cloud Practitioner Journey
Understanding the AWS Certified Cloud Practitioner Exam
Not taking practice exams, which are crucial for time management and question familiarity.
Getting Started: Your Cloud Practitioner Journey
Foundational Tier
Entry-level certifications, like Cloud Practitioner, for basic AWS knowledge.
Getting Started: Your Cloud Practitioner Journey
Associate Tier
Role-based certifications (e.g., Architect, Developer) requiring technical skills.
Getting Started: Your Cloud Practitioner Journey
Professional Tier
Advanced role-based certifications for complex AWS solution design/implementation.
Getting Started: Your Cloud Practitioner Journey
Specialty Tier
Certifications for deep expertise in specific AWS technical domains.
Getting Started: Your Cloud Practitioner Journey
Prerequisite
A condition or certification that must be met before attempting another.
Getting Started: Your Cloud Practitioner Journey
Validation
The process of confirming skills and knowledge through a certification exam.
Getting Started: Your Cloud Practitioner Journey
Navigating the AWS Certification Path
Remember the tiers with 'F-A-P-S': Foundational, Associate, Professional, Specialty. It's like climbing a ladder to cloud expertise!
Getting Started: Your Cloud Practitioner Journey
Navigating the AWS Certification Path
The Cloud Practitioner exam (CLF-C02) focuses on a broad understanding of AWS, its value proposition, and core services. While not directly testing the certification path, understanding that it's the 'foundational' certification helps frame the expected depth of knowledge.
Getting Started: Your Cloud Practitioner Journey
Navigating the AWS Certification Path
Skipping the Foundational Cloud Practitioner exam, assuming prior IT experience is enough, which can lead to gaps in AWS-specific concepts.
Getting Started: Your Cloud Practitioner Journey
Navigating the AWS Certification Path
Attempting a Professional or Specialty certification without sufficient hands-on experience, as these exams require deep practical knowledge.
Getting Started: Your Cloud Practitioner Journey
Navigating the AWS Certification Path
Focusing solely on exam dumps without truly understanding the concepts, which won't prepare you for real-world scenarios.
Getting Started: Your Cloud Practitioner Journey
Cloud Computing
On-demand delivery of IT resources over the internet with pay-as-you-go pricing.
Cloud Fundamentals: Concepts and Benefits
Public Cloud
Cloud services offered over the public internet by a third-party provider.
Cloud Fundamentals: Concepts and Benefits
Private Cloud
Cloud resources used exclusively by a single organization, on-prem or hosted.
Cloud Fundamentals: Concepts and Benefits
Hybrid Cloud
A mix of public and private cloud environments, sharing data and applications.
Cloud Fundamentals: Concepts and Benefits
IaaS
Infrastructure as a Service; provides virtualized computing resources over the internet.
Cloud Fundamentals: Concepts and Benefits
PaaS
Platform as a Service; provides a platform for developing, running, and managing applications.
Cloud Fundamentals: Concepts and Benefits
SaaS
Software as a Service; software applications hosted by a vendor and available over the internet.
Cloud Fundamentals: Concepts and Benefits
On-demand self-service
Users provision computing capabilities without human interaction from the service provider.
Cloud Fundamentals: Concepts and Benefits
Introduction to Cloud Computing and its Benefits
Remember the cloud service models with 'ISP': IaaS (Infrastructure), SaaS (Software), PaaS (Platform). Think of it like building a house: IaaS is buying the land and materials, PaaS is buying a pre-built foundation and frame, and SaaS is renting a fully furnished apartment.
Cloud Fundamentals: Concepts and Benefits
Introduction to Cloud Computing and its Benefits
The exam frequently tests the five essential characteristics of cloud computing (on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service) and the differences between IaaS, PaaS, and SaaS. Memorize what 'you' manage in each service model.
Cloud Fundamentals: Concepts and Benefits
Introduction to Cloud Computing and its Benefits
Confusing the responsibilities in IaaS, PaaS, and SaaS. Remember, IaaS gives you the most control, SaaS the least.
Cloud Fundamentals: Concepts and Benefits
Introduction to Cloud Computing and its Benefits
Mixing up public, private, and hybrid cloud definitions. Public is shared, private is exclusive, hybrid is both.
Cloud Fundamentals: Concepts and Benefits
Introduction to Cloud Computing and its Benefits
Forgetting the 'pay-as-you-go' aspect, which is a fundamental economic benefit of cloud computing.
Cloud Fundamentals: Concepts and Benefits
Well-Architected Framework
AWS best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable cloud systems.
Cloud Fundamentals: Concepts and Benefits
Operational Excellence
Pillar focused on running and monitoring systems to deliver business value and improving processes.
Cloud Fundamentals: Concepts and Benefits
Security Pillar
Pillar focused on protecting information, systems, and assets in the cloud.
Cloud Fundamentals: Concepts and Benefits
Reliability Pillar
Pillar focused on a system's ability to recover from outages and meet demand.
Cloud Fundamentals: Concepts and Benefits
Performance Efficiency
Pillar focused on using computing resources efficiently to meet system requirements.
Cloud Fundamentals: Concepts and Benefits
Cost Optimization
Pillar focused on avoiding unnecessary costs and optimizing cloud expenditure.
Cloud Fundamentals: Concepts and Benefits
Sustainability Pillar
Pillar focused on minimizing the environmental impacts of running cloud workloads.
Cloud Fundamentals: Concepts and Benefits
Infrastructure as Code (IaC)
Managing and provisioning infrastructure through code instead of manual processes.
Cloud Fundamentals: Concepts and Benefits
AWS Well-Architected Framework: Pillars of Success
Remember the pillars with 'SORCPS': Security, Operational Excellence, Reliability, Cost Optimization, Performance Efficiency, Sustainability. Or, 'S.O.R.P.C.S.' for 'Secure Operations Really Perform Cost-effectively, Sustainably!'
Cloud Fundamentals: Concepts and Benefits
AWS Well-Architected Framework: Pillars of Success
The exam often asks you to identify which pillar a specific scenario or solution relates to. Memorize the name and core focus of each of the six pillars. Keywords like 'automating operations' point to Operational Excellence, 'data protection' to Security, 'disaster recovery' to Reliability, 'right-sizing' to Performance Efficiency, 'cost savings' to Cost Optimization, and 'reducing carbon footprint' to Sustainability.
Cloud Fundamentals: Concepts and Benefits
AWS Well-Architected Framework: Pillars of Success
Confusing Reliability with Performance Efficiency: Reliability is about staying up and recovering, Performance Efficiency is about how fast and efficiently it runs.
Cloud Fundamentals: Concepts and Benefits
AWS Well-Architected Framework: Pillars of Success
Ignoring the framework until a problem arises: It's best used proactively during design and regularly for review, not just for troubleshooting.
Cloud Fundamentals: Concepts and Benefits
AWS Well-Architected Framework: Pillars of Success
Thinking it's a one-time checklist: The framework encourages continuous improvement and regular architectural reviews.
Cloud Fundamentals: Concepts and Benefits
AWS Cloud Adoption Framework (CAF)
Guidance for organizations to plan and implement cloud adoption.
Cloud Fundamentals: Concepts and Benefits
Rehost (Lift and Shift)
Migrating an application to the cloud without significant changes.
Cloud Fundamentals: Concepts and Benefits
Replatform (Lift and Reshape)
Migrating with minor cloud optimizations, like managed databases.
Cloud Fundamentals: Concepts and Benefits
Refactor/Rearchitect
Rebuilding an application to be cloud-native, maximizing cloud benefits.
Cloud Fundamentals: Concepts and Benefits
Repurchase (Drop and Shop)
Replacing an application with a cloud-based SaaS solution.
Cloud Fundamentals: Concepts and Benefits
Retire
Decommissioning applications that are no longer needed.
Cloud Fundamentals: Concepts and Benefits
Retain
Keeping certain applications on-premises due to specific reasons.
Cloud Fundamentals: Concepts and Benefits
Relocate
Hypervisor-level move of VMs, often for entire environments.
Cloud Fundamentals: Concepts and Benefits
Cloud Migration Strategies: The 7 Rs and CAF
To remember the 7 R's, think of '7 Ways to Relocate, Rebuild, or Remove your Apps': Rehost, Replatform, Refactor, Repurchase, Retire, Retain, Relocate.
Cloud Fundamentals: Concepts and Benefits
Cloud Migration Strategies: The 7 Rs and CAF
The exam often asks you to identify the best migration strategy for a given scenario. Look for keywords like 'minimal changes' (Rehost), 'minor optimizations' (Replatform), 'cloud-native' (Refactor), or 'replace with SaaS' (Repurchase). Also, remember the six perspectives of the CAF.
Cloud Fundamentals: Concepts and Benefits
Cloud Migration Strategies: The 7 Rs and CAF
Confusing Rehost with Replatform: Rehost is truly 'as-is,' while Replatform involves minor changes to leverage cloud services.
Cloud Fundamentals: Concepts and Benefits
Cloud Migration Strategies: The 7 Rs and CAF
Underestimating the effort for Refactor: While offering the most benefits, Refactor/Rearchitect is the most time-consuming and complex strategy.
Cloud Fundamentals: Concepts and Benefits
Cloud Migration Strategies: The 7 Rs and CAF
Ignoring the 'Retire' and 'Retain' options: Not every application needs to be migrated or rebuilt; some can be decommissioned or left on-premises.
Cloud Fundamentals: Concepts and Benefits
Capital Expenditure (CAPEX)
Upfront spending on fixed assets like hardware.
Cloud Fundamentals: Concepts and Benefits
Operational Expenditure (OPEX)
Ongoing costs for services, paid as consumed.
Cloud Fundamentals: Concepts and Benefits
Pay-as-you-go
Billing model where you pay only for resources used.
Cloud Fundamentals: Concepts and Benefits
Economies of scale
Cost advantages from increased production/volume.
Cloud Fundamentals: Concepts and Benefits
Elasticity
Ability to scale resources up or down automatically.
Cloud Fundamentals: Concepts and Benefits
Right-sizing
Matching resource capacity to actual workload demand.
Cloud Fundamentals: Concepts and Benefits
Global Infrastructure
Worldwide network of AWS data centers (Regions/AZs).
Cloud Fundamentals: Concepts and Benefits
Understanding Cloud Economics and Cost Savings
CAPEX is for CAPITAL (big money upfront), OPEX is for OPERATING (ongoing, smaller payments).
Cloud Fundamentals: Concepts and Benefits
Understanding Cloud Economics and Cost Savings
The exam frequently tests the distinction between CAPEX and OPEX. Remember that cloud computing primarily converts CAPEX into OPEX, allowing for variable costs and eliminating large upfront investments. Look for keywords like 'upfront cost,' 'fixed assets,' 'pay-as-you-go,' and 'variable expense.'
Cloud Fundamentals: Concepts and Benefits
Understanding Cloud Economics and Cost Savings
Confusing CAPEX with OPEX; remember CAPEX is upfront, OPEX is ongoing.
Cloud Fundamentals: Concepts and Benefits
Understanding Cloud Economics and Cost Savings
Ignoring the importance of right-sizing and assuming 'bigger is always better' for cloud resources.
Cloud Fundamentals: Concepts and Benefits
Understanding Cloud Economics and Cost Savings
Not understanding that economies of scale from cloud providers lead to lower costs for customers.
Cloud Fundamentals: Concepts and Benefits
Shared Responsibility Model
Defines security duties between AWS and customers.
Security and Compliance in the Cloud
Security 'of' the Cloud
AWS's responsibility for underlying infrastructure.
Security and Compliance in the Cloud
Security 'in' the Cloud
Customer's responsibility for data, apps, configuration.
Security and Compliance in the Cloud
Customer Data
Information stored or processed by the customer.
Security and Compliance in the Cloud
Compliance
Adhering to regulations and industry standards.
Security and Compliance in the Cloud
The AWS Shared Responsibility Model Explained
Remember 'OF' for AWS (OF the infrastructure) and 'IN' for YOU (IN your applications).
Security and Compliance in the Cloud
The AWS Shared Responsibility Model Explained
The exam often uses phrases like 'security of the cloud' (AWS's job) and 'security in the cloud' (customer's job). Memorize these exact phrases and associate them with their respective parties. Pay close attention to how responsibility shifts with different service models (IaaS, PaaS, SaaS).
Security and Compliance in the Cloud
The AWS Shared Responsibility Model Explained
Assuming AWS is responsible for all security in the cloud, leading to misconfigured resources.
Security and Compliance in the Cloud
The AWS Shared Responsibility Model Explained
Not understanding that customer responsibility changes based on the AWS service model (e.g., EC2 vs. S3).
Security and Compliance in the Cloud
The AWS Shared Responsibility Model Explained
Failing to implement proper IAM policies, encryption, or network configurations, believing AWS handles it automatically.
Security and Compliance in the Cloud
IAM User
An entity representing a person or application for AWS access.
Security and Compliance in the Cloud
IAM Group
A collection of IAM users that share the same permissions.
Security and Compliance in the Cloud
IAM Role
An identity with permissions that can be assumed by trusted entities.
Security and Compliance in the Cloud
IAM Policy
A JSON document defining permissions for AWS actions and resources.
Security and Compliance in the Cloud
Principle of Least Privilege
Granting only the minimum permissions required for a user or service.
Security and Compliance in the Cloud
Authentication
The process of verifying an identity (who you are).
Security and Compliance in the Cloud
Authorization
The process of determining what an authenticated identity can do.
Security and Compliance in the Cloud
IAM Essentials: Users, Groups, Roles, and Policies
Think of IAM like a 'Club Security System': Users are the 'Members', Groups are 'Member Tiers' (like VIP or General), Roles are 'Guest Passes' (temporary, for specific tasks), and Policies are the 'Club Rules' stating who can enter which rooms and use which facilities.
Security and Compliance in the Cloud
IAM Essentials: Users, Groups, Roles, and Policies
The exam often asks about the primary purpose of IAM, the difference between users and roles, and the concept of policies. Keywords to spot include 'who can do what', 'programmatic access', 'temporary credentials', and 'least privilege'. Remember IAM is a global service.
Security and Compliance in the Cloud
IAM Essentials: Users, Groups, Roles, and Policies
Using the AWS root user for daily administrative tasks instead of an IAM user with administrator permissions.
Security and Compliance in the Cloud
IAM Essentials: Users, Groups, Roles, and Policies
Granting overly broad permissions (e.g., 's3:*' on all resources) instead of following the principle of least privilege.
Security and Compliance in the Cloud
IAM Essentials: Users, Groups, Roles, and Policies
Hardcoding AWS access keys directly into applications or EC2 instances instead of using IAM roles.
Security and Compliance in the Cloud
AWS Shield
Managed DDoS protection service for AWS resources.
Security and Compliance in the Cloud
DDoS Attack
Distributed Denial of Service; overwhelms services with traffic.
Security and Compliance in the Cloud
AWS WAF
Web Application Firewall; protects web apps from common exploits.
Security and Compliance in the Cloud
SQL Injection
Web exploit inserting malicious SQL code into input fields.
Security and Compliance in the Cloud
AWS GuardDuty
Intelligent threat detection service using ML and log analysis.
Security and Compliance in the Cloud
AWS Inspector
Automated security assessment for vulnerabilities and compliance.
Security and Compliance in the Cloud
CVE
Common Vulnerabilities and Exposures; a public database.
Security and Compliance in the Cloud
Threat Intelligence
Information about potential or actual threats to assets.
Security and Compliance in the Cloud
AWS Security Services: Shield, WAF, GuardDuty, Inspector
To remember the services: **S**hield **W**ards off **G**uilty **I**ntruders. (Shield, WAF, GuardDuty, Inspector)
Security and Compliance in the Cloud
AWS Security Services: Shield, WAF, GuardDuty, Inspector
The exam often asks you to distinguish between these services. Remember: Shield is for DDoS, WAF is for web exploits (SQLi, XSS), GuardDuty is for intelligent threat detection from logs, and Inspector is for vulnerability scanning of EC2/containers.
Security and Compliance in the Cloud
AWS Security Services: Shield, WAF, GuardDuty, Inspector
Confusing Shield (DDoS) with WAF (web exploits). They operate at different layers.
Security and Compliance in the Cloud
AWS Security Services: Shield, WAF, GuardDuty, Inspector
Thinking GuardDuty actively blocks threats; it detects and alerts, requiring other services for blocking.
Security and Compliance in the Cloud
AWS Security Services: Shield, WAF, GuardDuty, Inspector
Believing Inspector fixes vulnerabilities; it only identifies them and provides recommendations.
Security and Compliance in the Cloud
AWS KMS
Managed service for creating and controlling encryption keys.
Security and Compliance in the Cloud
Customer Managed Key (CMK)
Encryption key in KMS that you create, own, and manage.
Security and Compliance in the Cloud
AWS Artifact
Central portal for AWS compliance reports and agreements.
Security and Compliance in the Cloud
AWS Security Hub
Centralized security posture management and alert aggregation.
Security and Compliance in the Cloud
AWS CloudTrail
Records AWS API calls and account activity for auditing.
Security and Compliance in the Cloud
AWS Config
Monitors and records AWS resource configurations over time.
Security and Compliance in the Cloud
FIPS 140-2
US government standard for cryptographic modules.
Security and Compliance in the Cloud
Compliance Reports
Documents proving adherence to industry standards/regulations.
Security and Compliance in the Cloud
Data Protection: KMS, Artifact, Security Hub, CloudTrail, Config
KMS = Keys for My Stuff. Artifact = All Regulatory Info For Audits. Security Hub = See All Security. CloudTrail = Track All Interactions Logged. Config = Configuration Changes.
Security and Compliance in the Cloud
Data Protection: KMS, Artifact, Security Hub, CloudTrail, Config
The exam often tests the specific purpose of each service. Remember KMS for encryption keys, Artifact for compliance documents, CloudTrail for API call logging/auditing, Config for resource configuration history/compliance, and Security Hub for aggregated security findings.
Security and Compliance in the Cloud
Data Protection: KMS, Artifact, Security Hub, CloudTrail, Config
Confusing CloudTrail (API activity logging) with CloudWatch (monitoring operational data like metrics and logs).
Security and Compliance in the Cloud
Data Protection: KMS, Artifact, Security Hub, CloudTrail, Config
Thinking AWS Artifact generates compliance reports; it only provides access to existing ones.
Security and Compliance in the Cloud
Data Protection: KMS, Artifact, Security Hub, CloudTrail, Config
Believing KMS encrypts data itself; it provides the keys, and other services use those keys for encryption.
Security and Compliance in the Cloud
Multi-Factor Authentication (MFA)
Security requiring multiple verification factors.
Security and Compliance in the Cloud
AWS Root User
The most powerful account with full access to all resources.
Security and Compliance in the Cloud
Identity-based Policies
Attached to IAM users, groups, or roles to grant permissions.
Security and Compliance in the Cloud
Resource-based Policies
Attached directly to a resource to control access to it.
Security and Compliance in the Cloud
Service Control Policies (SCPs)
Used in AWS Organizations to set maximum account permissions.
Security and Compliance in the Cloud
Explicit Deny
A policy statement that always overrides any Allow statements.
Security and Compliance in the Cloud
Virtual MFA Device
Software application generating time-based one-time passwords.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
Think of the Root User as the 'Master Key' to your house. You keep it in a very secure place (MFA, locked away) and only use it for emergencies. For daily entry, you use copies (IAM users) with specific permissions.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
For the CLF-C02 exam, remember that the Root User has full administrative access and cannot be restricted by IAM policies. However, SCPs in AWS Organizations can restrict the Root User's actions. Always enable MFA for the Root User and create an administrative IAM user for daily tasks.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
Using the AWS Root User for daily administrative tasks instead of an IAM user.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
Not enabling MFA on the AWS Root User account, leaving it vulnerable.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
Assuming an IAM policy will override a more restrictive Service Control Policy (SCP) or an explicit Deny.
Security and Compliance in the Cloud
MFA, Root User Best Practices, and Policy Enforcement
Confusing identity-based policies with resource-based policies.
Security and Compliance in the Cloud
EC2 Instance
A virtual server in the AWS cloud, providing resizable compute capacity.
Core AWS Technologies and Services
AMI
Amazon Machine Image; a template for EC2 instances, including OS and software.
Core AWS Technologies and Services
Lambda Function
A unit of code executed by AWS Lambda in response to events.
Core AWS Technologies and Services
Serverless
A cloud execution model where the cloud provider manages server infrastructure.
Core AWS Technologies and Services
Containerization
Packaging an application and its dependencies into a portable, isolated unit.
Core AWS Technologies and Services
ECS
Amazon Elastic Container Service; an AWS-native container orchestration service.
Core AWS Technologies and Services
EKS
Amazon Elastic Kubernetes Service; a managed Kubernetes service on AWS.
Core AWS Technologies and Services
Fargate
A serverless compute engine for containers, compatible with ECS and EKS.
Core AWS Technologies and Services
Compute Services: EC2, Lambda, ECS, EKS, Fargate
Think of 'E-C-2' as 'Easy-Compute-Too' much control. 'Lambda' is like a 'light switch' – it only turns on when an event happens! 'Fargate' is 'Far-Away-Gate' from managing servers.
Core AWS Technologies and Services
Compute Services: EC2, Lambda, ECS, EKS, Fargate
The exam often tests your ability to distinguish between serverless (Lambda, Fargate) and server-based (EC2, ECS/EKS on EC2) compute. Look for keywords like 'no servers to manage' or 'pay only for code execution' for serverless options. For EC2, keywords include 'full control over OS' or 'choose instance type'.
Core AWS Technologies and Services
Compute Services: EC2, Lambda, ECS, EKS, Fargate
Confusing serverless (Lambda, Fargate) with simply not seeing the servers (EC2 instances are still servers, even if virtual).
Core AWS Technologies and Services
Compute Services: EC2, Lambda, ECS, EKS, Fargate
Assuming all container services are serverless; ECS and EKS can run on EC2 instances you manage.
Core AWS Technologies and Services
Compute Services: EC2, Lambda, ECS, EKS, Fargate
Overlooking the cost implications: Lambda is billed per invocation and duration, while EC2 is typically per hour/second for the instance itself.
Core AWS Technologies and Services
Object Storage
Data stored as objects with metadata, accessed via API.
Core AWS Technologies and Services
Block Storage
Data stored in fixed-size blocks, like a traditional hard drive.
Core AWS Technologies and Services
File Storage
Data stored in a hierarchical file system, shared by multiple clients.
Core AWS Technologies and Services
Durability
The likelihood of data remaining intact and uncorrupted over time.
Core AWS Technologies and Services
Availability Zone (AZ)
One or more discrete data centers with redundant power, networking, and connectivity.
Core AWS Technologies and Services
S3 Bucket
A container for objects stored in Amazon S3.
Core AWS Technologies and Services
EBS Volume
A persistent block storage device for EC2 instances.
Core AWS Technologies and Services
S3 Glacier
A low-cost Amazon S3 storage class for data archiving.
Core AWS Technologies and Services
Storage Solutions: S3, EBS, EFS, and Storage Classes
Think of S3 as a 'Super Storage Shelf' for anything, EBS as an 'EC2's Best Friend' hard drive, and EFS as an 'Easy File Share' for many EC2s.
Core AWS Technologies and Services
Storage Solutions: S3, EBS, EFS, and Storage Classes
The exam frequently asks to identify the best storage service for a given scenario. Keywords like 'object storage,' 'static website,' 'backup' point to S3. 'EC2 root volume,' 'database,' 'low-latency block storage' point to EBS. 'Shared file system,' 'multiple EC2 instances access same data' point to EFS. Memorize the 11 nines durability for S3.
Core AWS Technologies and Services
Storage Solutions: S3, EBS, EFS, and Storage Classes
Confusing EBS (block storage for a single EC2) with EFS (shared file storage for multiple EC2s).
Core AWS Technologies and Services
Storage Solutions: S3, EBS, EFS, and Storage Classes
Using S3 Standard for long-term archives when S3 Glacier would be significantly cheaper.
Core AWS Technologies and Services
Storage Solutions: S3, EBS, EFS, and Storage Classes
Trying to mount an S3 bucket directly as a file system on an EC2 instance (it's object storage, not file storage).
Core AWS Technologies and Services
Amazon RDS
Managed relational database service supporting multiple engines.
Core AWS Technologies and Services
Amazon Aurora
High-performance, MySQL/PostgreSQL-compatible relational database.
Core AWS Technologies and Services
Amazon DynamoDB
Fully managed NoSQL key-value and document database.
Core AWS Technologies and Services
Relational Database
Database that stores data in tables with predefined schemas and relationships.
Core AWS Technologies and Services
NoSQL Database
Database offering flexible schemas, designed for high scalability and performance.
Core AWS Technologies and Services
Multi-AZ
Deployment option for RDS for high availability and disaster recovery.
Core AWS Technologies and Services
Read Replica
Copies of your database to offload read traffic and improve performance.
Core AWS Technologies and Services
Database Services: RDS, Aurora, and DynamoDB
R-A-D: Relational for Aurora/RDS, Anything else for DynamoDB. If it's structured and needs relationships, think R-A. If it's flexible and needs speed at scale, think D.
Core AWS Technologies and Services
Database Services: RDS, Aurora, and DynamoDB
The exam often tests your understanding of use cases. Keywords like 'structured data,' 'ACID transactions,' and 'complex queries' point to RDS/Aurora. 'Flexible schema,' 'high throughput,' 'low latency at any scale,' and 'key-value' point to DynamoDB.
Core AWS Technologies and Services
Database Services: RDS, Aurora, and DynamoDB
Confusing the fully managed nature of these services with needing to manage the underlying EC2 instances yourself. AWS handles the infrastructure.
Core AWS Technologies and Services
Database Services: RDS, Aurora, and DynamoDB
Assuming Aurora is a separate database engine entirely; it's compatible with MySQL and PostgreSQL.
Core AWS Technologies and Services
Database Services: RDS, Aurora, and DynamoDB
Choosing a relational database for a use case that clearly benefits from a NoSQL database, or vice-versa, due to misunderstanding their core strengths.
Core AWS Technologies and Services
VPC
Logically isolated section of the AWS Cloud for your resources.
Core AWS Technologies and Services
Subnet
A range of IP addresses in your VPC.
Core AWS Technologies and Services
Security Group
Acts as a virtual firewall for EC2 instances.
Core AWS Technologies and Services
Network ACL (NACL)
Optional layer of security for subnets.
Core AWS Technologies and Services
CloudFront
Global Content Delivery Network (CDN) service.
Core AWS Technologies and Services
Edge Location
Data centers used by CloudFront to cache content.
Core AWS Technologies and Services
Route 53
Scalable cloud Domain Name System (DNS) web service.
Core AWS Technologies and Services
DNS
Translates domain names to IP addresses.
Core AWS Technologies and Services
Networking & Content Delivery: VPC, CloudFront, Route 53
Imagine a 'V'an 'P'arking 'C'omplex (VPC) as your private garage. A 'Cloud' 'Front' (CloudFront) is like a global express delivery service for your packages. 'Route 53' is the GPS that tells everyone where to send their requests.
Core AWS Technologies and Services
Networking & Content Delivery: VPC, CloudFront, Route 53
The exam often tests the distinct functions: VPC for network isolation and control, CloudFront for global content caching and delivery, and Route 53 for domain name resolution and traffic routing. Look for keywords like 'private network', 'IP addresses', 'subnets' for VPC; 'low latency', 'global delivery', 'caching', 'edge locations' for CloudFront; and 'domain name', 'DNS', 'traffic routing', 'health checks' for Route 53.
Core AWS Technologies and Services
Networking & Content Delivery: VPC, CloudFront, Route 53
Confusing Security Groups (instance level) with Network ACLs (subnet level) in VPC.
Core AWS Technologies and Services
Networking & Content Delivery: VPC, CloudFront, Route 53
Thinking CloudFront is only for static content; it can also deliver dynamic content and APIs.
Core AWS Technologies and Services
Networking & Content Delivery: VPC, CloudFront, Route 53
Underestimating Route 53's advanced routing capabilities beyond simple DNS resolution.
Core AWS Technologies and Services
Amazon SQS
Fully managed message queuing service for decoupling application components.
Core AWS Technologies and Services
Queue
A temporary storage location for messages awaiting processing by a consumer.
Core AWS Technologies and Services
Amazon SNS
Fully managed messaging service for broadcasting messages to multiple subscribers.
Core AWS Technologies and Services
Topic
An access point for publishers to send messages and subscribers to receive them in SNS.
Core AWS Technologies and Services
Fan-out messaging
A pattern where a single message is sent to multiple destinations or subscribers.
Core AWS Technologies and Services
Amazon CloudWatch
Monitoring and observability service for AWS resources and applications.
Core AWS Technologies and Services
Metric
A time-ordered set of data points representing a variable to be monitored.
Core AWS Technologies and Services
CloudWatch Alarm
A mechanism to perform actions when a metric crosses a specified threshold.
Core AWS Technologies and Services
Messaging, Monitoring, and Deployment: SQS, SNS, CloudWatch
SQS is for 'Queueing Stuff Slowly.' SNS is for 'Sending Notifications Swiftly.' CloudWatch is for 'Watching Closely.'
Core AWS Technologies and Services
Messaging, Monitoring, and Deployment: SQS, SNS, CloudWatch
The exam often tests your understanding of when to use SQS versus SNS. Remember: SQS is for one-to-one (or one-to-many with multiple consumers pulling from the same queue) asynchronous communication and decoupling, often for processing. SNS is for one-to-many fan-out notifications and broadcasting. CloudWatch is for monitoring and reacting to events.
Core AWS Technologies and Services
Messaging, Monitoring, and Deployment: SQS, SNS, CloudWatch
Confusing SQS (pull-based, decoupling) with SNS (push-based, fan-out notifications).
Core AWS Technologies and Services
Messaging, Monitoring, and Deployment: SQS, SNS, CloudWatch
Assuming CloudWatch directly handles application communication; it monitors it.
Core AWS Technologies and Services
Messaging, Monitoring, and Deployment: SQS, SNS, CloudWatch
Not understanding the difference between SQS Standard (best-effort ordering) and FIFO (guaranteed ordering, exactly-once processing) queues.
Core AWS Technologies and Services
Reserved Instances (RIs)
Commitment to consistent usage for discounted rates (1 or 3 years).
Billing, Pricing, and Support
Savings Plans
Flexible commitment to compute usage for discounted rates.
Billing, Pricing, and Support
Volume Discounts
Lower per-unit cost as usage of a service increases.
Billing, Pricing, and Support
AWS Cost Explorer
Tool for visualizing and analyzing AWS costs and usage.
Billing, Pricing, and Support
AWS Budgets
Sets custom budgets and alerts for cost or usage thresholds.
Billing, Pricing, and Support
AWS Pricing Calculator
Estimates costs for planned AWS architectures.
Billing, Pricing, and Support
Data Egress
Data transferred out from AWS to the internet, typically charged.
Billing, Pricing, and Support
AWS Pricing Models and Cost Management Tools
To remember the three pricing models, think 'P-S-V': Pay-as-you-go, Save when you reserve, Volume discounts. Like a PSV (PlayStation Vita) that helps you game on a budget!
Billing, Pricing, and Support
AWS Pricing Models and Cost Management Tools
The exam often asks about the fundamental pricing models and the purpose of key cost management tools. Memorize the three core pricing models (Pay-as-you-go, Save when you reserve, Pay less with volume) and the primary function of Cost Explorer, Budgets, and Pricing Calculator. Understand that data ingress is mostly free, while egress is usually charged.
Billing, Pricing, and Support
AWS Pricing Models and Cost Management Tools
Forgetting that data transfer OUT of AWS to the internet is almost always charged.
Billing, Pricing, and Support
AWS Pricing Models and Cost Management Tools
Not understanding the difference between Reserved Instances (specific instance types) and Savings Plans (more flexible compute commitment).
Billing, Pricing, and Support
AWS Pricing Models and Cost Management Tools
Failing to use AWS Budgets, leading to unexpected high bills from forgotten resources.
Billing, Pricing, and Support
Cost Forecasting
Predicting future AWS costs based on historical data.
Billing, Pricing, and Support
Budget Threshold
A predefined spending limit that triggers an alert.
Billing, Pricing, and Support
Usage Tracking
Monitoring the consumption of AWS resources.
Billing, Pricing, and Support
Cost Explorer, Budgets, and Pricing Calculator
Imagine a 'CAB' for your costs: 'C'ost Explorer for analysis, 'A'WS Budgets for alerts, 'B'udget Calculator for new estimates.
Billing, Pricing, and Support
Cost Explorer, Budgets, and Pricing Calculator
The exam often presents scenarios asking which tool best fits a specific cost management need. Remember: 'Estimate' = Pricing Calculator, 'Analyze historical' = Cost Explorer, 'Alerts/Prevent overspending' = Budgets.
Billing, Pricing, and Support
Cost Explorer, Budgets, and Pricing Calculator
Confusing Cost Explorer's historical analysis with the Pricing Calculator's future estimation.
Billing, Pricing, and Support
Cost Explorer, Budgets, and Pricing Calculator
Not setting up alerts in AWS Budgets, relying only on manual checks.
Billing, Pricing, and Support
Cost Explorer, Budgets, and Pricing Calculator
Forgetting that the AWS Pricing Calculator is for *new* estimates, not for tracking current spend.
Billing, Pricing, and Support
AWS Organizations
Service for centrally managing multiple AWS accounts.
Billing, Pricing, and Support
Management Account
The primary account that controls an AWS Organization.
Billing, Pricing, and Support
Member Account
Any AWS account that is part of an AWS Organization.
Billing, Pricing, and Support
Consolidated Billing
Single bill for all accounts in an organization, with volume discounts.
Billing, Pricing, and Support
Organizational Unit (OU)
A logical grouping of AWS accounts within an organization.
Billing, Pricing, and Support
Service Control Policy (SCP)
Policy that defines maximum permissions for accounts or OUs.
Billing, Pricing, and Support
Volume Pricing
Discounts based on aggregate usage across all accounts.
Billing, Pricing, and Support
AWS Organizations and Consolidated Billing
Remember 'ORGANIZE' your accounts: OUs for groupings, Root for the top, Global policies (SCPs), and Integrated billing.
Billing, Pricing, and Support
AWS Organizations and Consolidated Billing
Consolidated billing offers volume discounts, which means the more you use across all accounts in your organization, the less you pay per unit. SCPs only set maximum permissions; they do not grant permissions.
Billing, Pricing, and Support
AWS Organizations and Consolidated Billing
Confusing SCPs with IAM policies: SCPs set maximum permissions, IAM policies grant actual permissions.
Billing, Pricing, and Support
AWS Organizations and Consolidated Billing
Believing consolidated billing means all costs are free: It aggregates billing and offers discounts, but you still pay for usage.
Billing, Pricing, and Support
AWS Organizations and Consolidated Billing
Assuming member accounts have full control over their own billing: The management account handles the consolidated bill.
Billing, Pricing, and Support
AWS Support Plans
Subscription services offering varying levels of technical assistance and guidance from AWS.
Billing, Pricing, and Support
Basic Support
Free plan with customer service, documentation, and Personal Health Dashboard access.
Billing, Pricing, and Support
Business Support
24/7 phone/chat/email support for production workloads, with faster response times.
Billing, Pricing, and Support
Enterprise Support
Highest support level with a dedicated Technical Account Manager (TAM) and proactive guidance.
Billing, Pricing, and Support
Technical Account Manager (TAM)
A dedicated expert who provides proactive guidance and strategic support for Enterprise plans.
Billing, Pricing, and Support
AWS Trusted Advisor
An online tool providing real-time guidance on best practices for cost, performance, security, fault tolerance, and service limits.
Billing, Pricing, and Support
Personal Health Dashboard
Provides personalized view of the health of AWS services and alerts for events impacting your resources.
Billing, Pricing, and Support
Response Time SLA
Guaranteed maximum time for AWS Support to respond to a technical issue based on severity.
Billing, Pricing, and Support
AWS Support Plans and Trusted Advisor
To remember Trusted Advisor's categories, think 'CPS-FT': Cost, Performance, Security, Fault Tolerance, Service Limits. It's like a 'CPS' (Child Protective Services) for your 'FT' (Fault Tolerant) cloud!
Billing, Pricing, and Support
AWS Support Plans and Trusted Advisor
Memorize the key features and response times for Business and Enterprise Support. For Trusted Advisor, remember the five categories of checks (Cost Optimization, Performance, Security, Fault Tolerance, Service Limits) and which checks are available for all customers (Security, Service Limits).
Billing, Pricing, and Support
AWS Support Plans and Trusted Advisor
Underestimating the importance of a higher support plan for production workloads, leading to extended downtime during critical issues.
Billing, Pricing, and Support
AWS Support Plans and Trusted Advisor
Not regularly reviewing AWS Trusted Advisor reports, missing opportunities to optimize costs, improve security, or enhance performance.
Billing, Pricing, and Support
AWS Support Plans and Trusted Advisor
Confusing the features of Developer Support with Business Support, especially regarding 24/7 access and critical issue response times.
Billing, Pricing, and Support