Free CLF-C02 Practice Questions

Incorrect Options:

• Global infrastructure
  This refers to AWS's availability zones and regions worldwide, not directly to cost efficiency through scaling.
• Pay-as-you-go pricing
  This model lets you avoid upfront costs and only pay for what you use, but it does not explain why prices drop as AWS grows.
• Operational excellence
  This is a pillar of the AWS Well-Architected Framework and refers to best practices for operations—not cost benefits due to customer volume.

Incorrect Options:

• Cost Optimization
  This pillar focuses on minimizing expenses and maximizing ROI—not maintaining uptime or handling failures.
• Operational Excellence
  Operational excellence is about running and monitoring systems effectively and evolving them over time, not directly about failure recovery or scaling.
• Performance Efficiency
  While this includes choosing the right resource types and scaling based on demand, it does not cover automatic failure recovery, which is central to the Reliability pillar.

Incorrect Options:

• Increased revenue
  Although AWS CAF can lead to revenue gains in the long run by enabling digital transformation, that’s not its primary focus when addressing regulatory or disruption concerns.
• Improved customer experience
  A smoother migration might improve experience, but that’s a secondary effect. CAF's goal here is to mitigate internal risk.
• Enhanced scalability
  AWS services offer scalability, but CAF’s role is not technical implementation—it’s strategic planning, particularly around risk and governance.

Incorrect Options:

• Using Bring Your Own License (BYOL) to reduce dependency on AWS-provided pricing
  BYOL may help with vendor flexibility but doesn't solve infrastructure scaling or reduce capital expenditures.
• Prepaying with Reserved Instances to lock in lower compute rates
  This provides savings only after usage becomes predictable; not ideal for startups expecting uncertain growth.
• Running servers at full capacity to avoid waste from idle resources
  This only masks inefficiencies and does not accommodate future scaling or reduce upfront costs.

Incorrect Options:

• Managing the security of the underlying hardware that EC2 runs on
  This is AWS’s responsibility as part of their commitment to secure the infrastructure of the cloud.
• Ensuring the global availability of EC2 services
  AWS ensures service availability and resilience across its global infrastructure—not the customer.
• Physically securing the AWS data center where the EC2 instance is located
  Customers never handle physical security of AWS facilities. That’s entirely managed by AWS.

Incorrect Options:

• AWS CloudTrail
  Tracks API activity and is used for security log auditing, not compliance report access.
• AWS Config
  Evaluates configuration compliance of resources over time but does not provide audit reports.
• AWS Security Hub
  Aggregates and prioritizes security findings, not compliance documents or logs.

Incorrect Options:

• Create IAM users in each account and rotate credentials monthly
  This creates management overhead and risks inconsistent access policies across accounts.
• Use AWS Secrets Manager to store static credentials for each engineer
  Secrets Manager is for managing credentials, not for assigning access. It doesn't enforce least privilege by itself.
• Attach AdministratorAccess directly to engineer IAM roles in every account
  This violates least privilege, granting far more access than needed and increasing the attack surface.

Incorrect Options:

• Use AWS Knowledge Center for troubleshooting guides:
  The AWS Knowledge Center provides troubleshooting guides but is not focused on security documentation.
• Use AWS Security Hub for security compliance reports:
  AWS Security Hub aggregates security findings but does not provide in-depth security documentation or resources.
• Use AWS Security Center for security resources and news:
  AWS Security Center offers some security-related information but is less comprehensive for best practices and updates compared to the AWS Security Blog.

Incorrect Options:

• Use the AWS Management Console to create and manage resources:
  The AWS Management Console is a GUI for managing AWS resources. It is not efficient for large-scale or repeatable infrastructure management, especially across multiple environments.
• Use the AWS CLI to script the creation of resources programmatically:
  While the AWS CLI allows for automation, it lacks the version-controlled, repeatable, and declarative nature of Infrastructure as Code tools, which provide a better way to manage complex environments.
• Use the AWS SDKs to automate resource management with code:
  AWS SDKs enable programmatic access to AWS services, but they are generally more useful for application-level integration rather than infrastructure provisioning, which is better handled by IaC tools like CloudFormation.

Incorrect Options:

• Use AWS Local Zones in multiple Regions for low-latency access:
  AWS Local Zones bring compute and storage closer to users but are limited to specific locations and do not provide a global traffic routing solution like Global Accelerator.
• Use multiple Availability Zones in a single Region for redundancy:
  Multiple Availability Zones improve high availability within a single Region, but they do not help with minimizing latency or ensuring availability across multiple Regions.
• Use AWS Wavelength Zones for low-latency 5G applications:
  AWS Wavelength Zones are designed for ultra-low-latency applications at the edge of 5G networks, but they are focused on specific use cases like 5G rather than global high-availability strategies.

Incorrect Options:

• Amazon Aurora for MySQL with automated management:
  Aurora is a high-performance MySQL-compatible database that offers similar features to RDS, but it is more specialized for higher scalability and performance. While it’s a great choice for demanding workloads, RDS for MySQL is a simpler, fully managed solution for less intensive applications.
• Amazon DynamoDB for relational workloads:
  DynamoDB is a NoSQL database, not a relational database. It is optimized for key-value and document data models and is not suited for relational workloads like MySQL.
• Amazon Redshift for complex queries and analytics:
  Redshift is a managed data warehouse designed for analytics, not for transactional relational databases. It is not suitable for general relational database use cases like RDS for MySQL.

Incorrect Options:

• Amazon Simple Queue Service (Amazon SQS):
  Amazon SQS is a message queue service, designed for decoupling application components and ensuring reliable message delivery. It is not used for immediate notifications but for storing and processing messages asynchronously.
• Amazon WorkSpaces Web:
  Amazon WorkSpaces Web is a service for providing browser-based access to Amazon WorkSpaces desktops. It is not designed for sending messages or notifications.
• AWS Cloud9:
  AWS Cloud9 is an integrated development environment (IDE) for writing, running, and debugging code. It is not used for sending notifications or alerts.

Incorrect Options:

• On-Demand Instances:
  On-Demand Instances offer flexibility with no upfront commitment but are more expensive than Savings Plans for predictable, steady workloads.
• Reserved Instances:
  Reserved Instances provide savings for specific instance types and regions but are less flexible than Savings Plans since they require a commitment to a specific instance type.
• Capacity Reservations:
  Capacity Reservations ensure that you have guaranteed capacity in a specific Availability Zone but do not offer cost savings compared to other purchasing options like Reserved Instances or Savings Plans.

• AWS Budgets, AWS Cost Explorer, AWS Cost Allocation Tags:
  This combination is the most appropriate for tracking and managing costs across multiple departments. AWS Budgets helps set custom cost alerts and track spending, AWS Cost Explorer provides detailed cost and usage analysis, and AWS Cost Allocation Tags allow for granular tracking by department across multiple accounts in AWS Organizations. This setup ensures clear cost separation and budget control for each department.

Incorrect Options:

• AWS Budgets, AWS Cost Explorer, AWS Billing Conductor:
  While AWS Billing Conductor helps in customizing billing and pricing, it doesn’t provide the granular cost tracking by department that AWS Cost Allocation Tags can offer. This combination is not as suitable for managing department-level costs.
• AWS Cost Explorer, AWS Budgets, AWS Organizations:
  This combination misses out on using cost allocation tags for detailed tracking across departments. While AWS Organizations helps centralize billing, it doesn’t provide granular cost separation unless cost allocation tags are implemented.
• AWS Budgets, AWS Cost Explorer, AWS Trusted Advisor:
  AWS Trusted Advisor offers recommendations for optimizing AWS usage but doesn’t help with cost allocation or departmental budgeting. It's less useful for tracking specific department-level costs compared to AWS Cost Allocation Tags.

Incorrect Options:

• AWS Cost and Usage Report with AWS Pricing Calculator:
  The Cost and Usage Report provides detailed historical cost data but lacks visualization or real-time alerting capabilities. AWS Pricing Calculator helps estimate future service costs but doesn’t track actual usage or costs, making this combination incomplete for ongoing cost management.
• AWS Budgets with AWS Cost Explorer:
  While AWS Budgets is great for setting custom spending limits and alerts, it doesn’t provide detailed reporting on cost allocation tags. AWS Cost Explorer is essential for cost visualization but lacks the granularity provided by the Cost and Usage Report for in-depth analysis.
• AWS Pricing Calculator with AWS Budgets:
  AWS Pricing Calculator helps estimate costs for future AWS services, but it doesn't track historical costs or provide a detailed breakdown of costs by department. AWS Budgets is ideal for setting thresholds and alerts but doesn’t provide the necessary detailed reports on actual costs.

Incorrect Options:

• AWS Knowledge Center:
  The AWS Knowledge Center provides a repository of articles that answer frequently asked questions and help resolve common technical issues. While helpful for troubleshooting, it doesn't offer the detailed guidance and frameworks needed for large-scale solution implementation.
• AWS Support Center:
  The AWS Support Center is focused on managing support cases, submitting requests, and tracking issues related to AWS services. It is a customer support platform, not a resource for prescriptive, best-practice guidance.
• AWS re:Post:
  AWS re:Post is a community-driven Q&A platform where users can ask and answer technical questions related to AWS. While it can provide valuable insights, it doesn't offer structured frameworks or prescriptive guidance for building architectures.