AWS CCP-Exam

AWS Exam

1. Cloud Concepts (24% of Exam Content)
   Benefits of the AWS Cloud:

• Scalability: Automatically adjusts resources based on demand.
• Elasticity: Dynamically increases or decreases resources.
• Cost Efficiency: Pay-as-you-go pricing minimizes upfront costs.
• High Availability: Designed for fault tolerance using multiple Availability Zones.
• Global Reach: AWS has data centers globally for low latency.
• Agility: Faster time to market with quick deployments.
• Good to Use: For flexible and responsive cloud solutions with varying workloads.
• Not Good to Use: For applications that require fixed, long-term resources without fluctuation in demand.

⠀

2. Security and Compliance (30% of Exam Content)

AWS Shared Responsibility Model:

• AWS Responsibilities: Security of the cloud (physical infrastructure, networking, hardware).
• Customer Responsibilities: Security in the cloud (data, identity management, configurations).
• Shared Responsibility: AWS secures infrastructure, customers handle data protection and access management.
• Good to Use: To understand security obligations on AWS.
• Not Good to Use: Assuming AWS handles all security without customer responsibility.

⠀Identity and Access Management (IAM):

• Roles and Policies: Defines permissions for users and resources.
• Multi-Factor Authentication (MFA): Adds extra security.
• Good to Use: For implementing granular access control.
• Not Good to Use: Using default settings without customizing permissions.

⠀

3. Cloud Technology and Services (34% of Exam Content)

Compute Services:

• Amazon EC2: Scalable virtual machines.
• AWS Lambda: Serverless compute service that automatically runs code in response to events and scales based on demand.
  • Good to Use: For event-driven tasks like image processing or short-lived applications.
  • Not Good to Use: For long-running tasks exceeding 15 minutes.
• Amazon EKS: Managed Kubernetes for container orchestration.

⠀Database Services:

• Amazon RDS: Managed relational databases.
• Amazon DynamoDB: Fully managed NoSQL database.
• AWS DMS (Database Migration Service): Facilitates minimal downtime migration.

⠀Relational vs. NoSQL Databases:

• Relational Databases (RDS): Structured data with predefined schemas; supports complex queries.
• NoSQL Databases (DynamoDB): Schema-less storage for unstructured data with high scalability and flexible data models.
  • Good to Use: RDS for structured data needing complex queries; DynamoDB for high-volume, low-latency applications.
  • Not Good to Use: RDS for applications that require flexible schemas and high scalability.

⠀Storage Services:

• Amazon S3: Object storage for all sizes.
• Amazon EBS: Block storage for EC2 instances.
• Amazon EFS: Scalable file storage accessible by multiple EC2 instances.
  • Good to Use: S3 for large datasets and backups, EBS for high-performance needs tied to EC2, and EFS for file sharing.
  • Not Good to Use: EBS for data accessed by multiple instances.

⠀Amazon Cognito:

• Good to Use: For apps requiring secure user authentication.
• Not Good to Use: For apps without user authentication needs.

⠀AWS Transfer Family:

• Good to Use: For secure file exchanges with external partners.
• Not Good to Use: For file transfers not requiring secure protocols.

⠀

4. EBS Volume Types

Amazon Elastic Block Store (EBS):

• General Purpose SSD (gp2): Balanced price/performance for transactional workloads.
  • Good to Use: Development and testing environments.
  • Not Good to Use: For high IOPS applications.
• Throughput Optimized HDD (st1): Optimized for throughput-intensive workloads.
  • Good to Use: For high-throughput data sets like log processing or data warehousing.
  • Not Good to Use: For random I/O workloads.
• Provisioned IOPS SSD (io2): High-performance SSD for I/O-intensive workloads.
  • Good to Use: For transactional databases.
  • Not Good to Use: When cost is a concern.
• Cold HDD (sc1): Low-cost HDD for infrequently accessed data.
  • Good to Use: For archival storage.
  • Not Good to Use: For high-performance needs.

⠀

5. DDoS Protection Services

• AWS Shield: Protects against Distributed Denial of Service (DDoS) attacks.
  • Good to Use: For web applications requiring DDoS protection.
  • Not Good to Use: As a standalone security solution.
• AWS WAF (Web Application Firewall): Protects against common web exploits like SQL injection and cross-site scripting (XSS).
  • Good to Use: To filter malicious traffic.
  • Not Good to Use: As a complete security solution.

⠀

6. Monitoring and Management

• Amazon CloudWatch: A monitoring and observability service for AWS applications.
  • Good to Use: For monitoring performance, setting alarms, and centralizing logs.
  • Not Good to Use: For simple setups where minimal monitoring is needed.
• Amazon CloudWatch Alarms: Set up alarms to monitor system performance and trigger notifications or actions.
  • Good to Use: For automated responses to system thresholds.
  • Not Good to Use: For environments where manual monitoring suffices.
• Amazon CloudWatch Logs: Aggregate and analyze logs from multiple AWS services.
  • Good to Use: For comprehensive log analysis and monitoring.
  • Not Good to Use: For minimal log data that doesn’t require centralization.

7. AWS Cost and Billing Tools

• AWS Cost Explorer: Visualizes AWS cost and usage over time.
• AWS Budgets: Helps set custom cost and usage budgets.
• AWS Billing Conductor: Advanced cost management and chargeback scenarios.
• AWS Pricing Calculator: Estimates service costs.
  • Good to Use: For budgeting and predicting costs.
  • Not Good to Use: When you have minimal or predictable costs.

⠀

8. AWS Migration and Transfer Services

• AWS Database Migration Service (DMS): Helps migrate databases with minimal downtime.
• AWS Snow Family: Physical devices to move large datasets.
• AWS Application Migration Service: Automates the migration of applications.
  • Good to Use: For large on-premises data migrations.
  • Not Good to Use: For small-scale migrations.

⠀

9. AWS Marketplace

• Good to Use: For organizations needing third-party solutions.
• Not Good to Use: For custom-built solutions without third-party software needs.

⠀

10. AWS Direct Connect

• Good to Use: For low-latency and secure, dedicated connectivity.
• Not Good to Use: For smaller workloads that don’t justify the cost.

⠀

11. Amazon Managed Streaming for Apache Kafka (MSK)

• Good to Use: For real-time data streams and event-driven architectures.
• Not Good to Use: For simpler data stream requirements where Kinesis might suffice.

⠀

12. Amazon EventBridge

• Good to Use: For building event-driven architectures.
• Not Good to Use: When complex event-based integrations aren’t needed.

⠀

13. Amazon OpenSearch Service

• Good to Use: For log analytics, search, and real-time monitoring.
• Not Good to Use: For small datasets that don’t require powerful search or analytics features.

⠀

14. AWS Security Services

• AWS GuardDuty: Monitors malicious activity in your AWS environment.
• AWS Security Hub: Provides a comprehensive view of security alerts and compliance status.
• AWS Shield: Protects against DDoS attacks.
• AWS Secrets Manager: Manages access to secrets securely.
  • Good to Use: For large-scale environments.
  • Not Good to Use: In simple, low-risk environments.

⠀

15. Machine Learning Services

• Amazon SageMaker: A comprehensive service for building, training, and deploying machine learning models.
• Amazon Rekognition: Provides image and video analysis (e.g., facial recognition, object detection).
  • Good to Use: For machine learning workflows or image analysis applications.
  • Not Good to Use: When no machine learning capabilities are needed.

⠀

16. Well-Architected Framework

A set of best practices for designing reliable, secure, efficient, and cost-effective systems on AWS.

• Operational Excellence: Focuses on running and monitoring systems.
• Security: Protect information and systems.
• Reliability: Ensure workloads perform as expected.
• Performance Efficiency: Use resources efficiently.
• Cost Optimization: Minimize costs while maintaining functionality.
• Sustainability: Reduce environmental impact.
  • Good to Use: For scalable, secure, and efficient systems.
  • Not Good to Use: For small-scale applications where simplicity is more important.

⠀

17. AWS Support Plans

Enterprise Plan:

• 24/7 access to Senior Cloud Support Engineers.
• Response times of less than 15 minutes for critical issues.
• Access to a Technical Account Manager (TAM) for proactive support.
  • Good to Use: For organizations with mission-critical systems.

⠀Business Plan:

• 24/7 access to Cloud Support Engineers.
• Response times of less than 1 hour for urgent issues.
  • Good to Use: For businesses needing 24/7 support but no TAM.

⠀Developer Plan:

• Access to Cloud Support Associates during business hours.
• Response times within 12-24 hours.
  • Good to Use: For early-stage projects or development environments needing support during business hours.

⠀Basic Plan:

• Free of charge, no technical support, and access to AWS documentation.
  • Good to Use: For non-production environments that don’t require technical support.