Amazon Web Services Updated CLF-C02 Exam Questions and Answers by zian

AWS Application Composer is a service that allows users to visually design and build serverless applications. Users can drag and drop components, such as AWS Lambda functions, Amazon API Gateway endpoints, Amazon DynamoDB tables, and Amazon S3 buckets, to create aserverless application architecture. Users can also configure the properties, permissions, and dependencies of each component, and deploy the application to their AWS account with a few clicks. AWS Application Composer simplifies the design and configuration of serverless applications, and reduces the need to write code or use AWS CloudFormation templates. References: AWS Application Composer, AWS releases Application Composer to make serverless ‘easier’ but initial scope is limited

According to the AWS shared responsibility model, AWS is responsible for the security of the cloud, while the customer is responsible for the security in the cloud. This means that AWS is responsible for protecting the infrastructure that runs all of the services offered in the AWS Cloud, such as the global network, the hardware, the software, and the facilities. The customer is responsible for properly configuring the security of the provided service, such as the guest operating system, the application software, the data, and the network traffic. For abstracted services, such as Amazon RDS, AWS operates the infrastructure layer, the operating system, and the database software, while the customer is responsible for managing their data, classifying their assets, and using IAM tools to apply the appropriate permissions12.

Therefore, the tasks that are the customer’s responsibility are:

Perform client-side data encryption: The customer is responsible for encrypting their data before sending it to AWS, and decrypting it after receiving it from AWS. This ensures that the data is protected in transit and at rest. AWS provides various encryption options, such as AWS Key Management Service (AWS KMS), AWS CloudHSM, and AWS Certificate Manager (ACM)3.

Configure IAM credentials: The customer is responsible for creating and managing IAM users, groups, roles, and policies that control the access to AWS resources and services. IAM credentials include user names, passwords, access keys, and permissions4.

The tasks that are not the customer’s responsibility are:

Establish the global infrastructure: AWS is responsible for building and maintaining the global network of regions, availability zones, and edge locations that provide low latency, high availability, and fault tolerance for the AWS Cloud5.

Secure edge locations: AWS is responsible for protecting the physical security of the edge locations, which are sites that deliver cached content to end users with improved performance6.

Patch Amazon RDS DB instances: AWS is responsible for applying patches and updates to the operating system and the database software of the Amazon RDS DB instances, which are managed relational database service for MySQL, PostgreSQL, Oracle, SQL Server, and Amazon Aurora. References:

Shared Responsibility Model - Amazon Web Services (AWS)

Shared responsibility model - Amazon Web Services: Risk and Compliance

Encryption - Amazon Web Services (AWS)

What Is IAM? - AWS Identity and Access Management

Global Infrastructure - Amazon Web Services (AWS)

Amazon CloudFront Features - Content Delivery Network (CDN)

[What Is Amazon Relational Database Service (Amazon RDS)? - Amazon Relational Database Service]

One of the key advantages of cloud computing is the ability totrade fixed expenses (like data centers and physical servers) for variable expenses. With AWS, companies pay only for the compute power, storage, and other resources they use, rather than investing heavily in on-premises infrastructure upfront. This reduces capital expenditure and helps lower overall costs.

Why other options are not suitable:

A. Go global in minutes: Refers to the ability to quickly deploy applications around the world, but does not directly reduce upfront costs.

B. Increase speed and agility: Refers to the ability to quickly scale and deploy resources, but is not directly related to cost reduction.

C. Benefit from massive economies of scale: Refers to AWS's ability to lower costs by leveraging its scale, but the primary advantage for reducing upfront costs is moving from fixed to variable expenses.

On-Demand Instances are the most cost-efficient pricing model for an uninterruptible workload that runs once a year for 24 hours. On-Demand Instances let you pay for compute capacity by the hour or second, depending on which instances you run. No long-term commitments or up-front payments are required. You can increase or decrease your compute capacity to meet the demands of your application and only pay the specified hourly rates for the instance you use1. This model is suitable for developing/testing applications with short-term or unpredictable workloads2. The other pricing models are not cost-efficient for this use case. Reserved Instances and Savings Plans require a commitment to a consistent amount of usage, in USD per hour, for a term of 1 or 3 years. They provide significant discounts compared to On-Demand Instances, but they are not flexible or scalable for workloads that run only once a year12. Spot Instances are the cheapest option, but they are not suitable for uninterruptible workloads, as they can be reclaimed by AWS at any time. They are recommended for applications that have flexible start and end times, or that are only feasible at very low compute prices12. Dedicated Instances are designed for compliance and licensing requirements, not for cost optimization. They are more expensive than the other options, as they run on single-tenant hardware12. References: Amazon EC2 – Secure and resizable compute capacity – AWS, Amazon EC2 - How AWS Pricing Works