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

Reserved Instances (RIs)offer a significant discount (up to 75%) compared to On-Demand pricing in exchange for committing to use AWS for a period of 1 or 3 years. This pricing model is ideal for applications with predictable usage patterns or long-term commitments, such as critical production systems that will be running for at least 3 years.

A. On-Demand Instances: Incorrect, as they provide flexibility without commitment but are more expensive over the long term.

C. Spot Instances: Incorrect, as they offer the lowest cost for non-critical, interruptible workloads but are not suitable for critical production systems due to their potential for sudden termination.

D. AWS Free Tier: Incorrect, as it provides limited free usage for certain AWS services for a short period (typically one year) and is not intended for long-term production workloads.

AWS Cloud References:

Amazon EC2 Reserved Instances

Best practices for using AWS Identity and Access Management (IAM) include:

B. Create individual IAM users: Each user should have their own IAM credentials to ensure accountability, control, and traceability. Sharing credentials can lead to security risks and difficulty in auditing.

E. Use groups to assign permissions to IAM users: Assigning permissions through IAM groups simplifies permission management. You can assign the necessary permissions to the group, and then add or remove users from the group as needed, rather than managing permissions for each user individually.

Why other options are not suitable:

A. Share access keys: Sharing access keys is a security risk and violates AWS security best practices. Each user should have their own credentials.

C. Use inline policies instead of customer-managed policies: Customer-managed policies are preferred over inline policies because they offer better control, reusability, and versioning.

D. Grant maximum privileges to IAM users: Granting the least privilege necessary is a best practice to reduce the risk of accidental or malicious actions.

According to the AWS shared responsibility model, AWS is responsible for security of the cloud, while customers are responsible for security in the cloud. This means that AWS is responsible for protecting the infrastructure that runs AWS services, such as hardware, software, networking, and facilities. Customers are responsible for managing their data, classifying their assets, and using IAM tools to apply the appropriate permissions. For abstracted services, such as Amazon DynamoDB, AWS operates the infrastructure layer, the operating system, and platforms, and provides customers with public endpoints to store and retrieve data. Customers are responsible for classifying their data, managing their encryption options, and configuring their access permissions. References: Shared Responsibility Model, Security and compliance in Amazon DynamoDB, [AWS Cloud Practitioner Essentials: Module 2 - Security in the Cloud]

Reducing Costs with AWS Cloud:

Capacity Adjustment (B):

Elasticity: AWS allows you to scale your resources up or down based on demand, which means you only pay for what you use. This reduces the cost of over-provisioning resources.

Auto Scaling: Automatically adjusts compute capacity based on usage, ensuring cost efficiency.

Eliminating On-Premises Costs (E):

No Infrastructure Maintenance: By using AWS, businesses do not need to invest in physical infrastructure or handle maintenance, reducing both capital and operational expenditures.

Managed Services: AWS offers managed services that reduce the need for in-house technical staff to manage and maintain infrastructure.

AWS Cloud Economics Center

AWS Benefits