Skip to Content

Amazon CLF-C02: Which design principles are included in reliability pillar of AWS Well-Architected Framework?

Table of Contents

Question

Which design principles are included in the reliability pillar of the AWS Well-Architected Framework? (Choose two.)

A. Automatically recover from failure.
B. Grant everyone access to increase AWS service quotas.
C. Stop guessing capacity.
D. Design applications to run in a single Availability Zone.
E. Plan to increase AWS service quotas first in a secondary AWS Region.

Answer

A. Automatically recover from failure.
C. Stop guessing capacity.

Explanation

The correct answers are A. Automatically recover from failure and C. Stop guessing capacity.

A brief explanation is as follows:

The reliability pillar of the AWS Well-Architected Framework encompasses the ability of a workload to perform its intended function correctly and consistently when it is expected to. It includes the ability to operate and test the workload through its total lifecycle.

The reliability pillar has five design principles that guide the best practices for implementing reliable workloads on AWS. They are:

  • Test recovery procedures. You should test how your workload recovers from failures regularly using game days or chaos engineering. This will help you identify and fix any issues before they affect your customers or business.
  • Automatically recover from failure. You should design your workload to detect and handle failures without human intervention. This will reduce the impact of failures and improve the availability and resilience of your workload.
  • Scale horizontally to increase aggregate workload availability. You should distribute your workload across multiple resources or servers, rather than relying on a single one. This will reduce the probability of a single point of failure and allow you to scale your workload according to demand.
  • Stop guessing capacity. You should use monitoring and automation to provision the optimal amount of resources for your workload, rather than guessing or overprovisioning. This will help you avoid capacity issues, such as running out of resources or wasting money on unused resources.
  • Manage change in automation. You should use automation tools and processes to apply changes to your workload, rather than manual actions. This will help you reduce human errors, ensure consistency, and speed up deployments.

Option A is correct because automatically recovering from failure is one of the design principles of the reliability pillar.

Option B is incorrect because granting everyone access to increase AWS service quotas is not a design principle of the reliability pillar, nor a best practice for any pillar. AWS service quotas are limits on the usage of certain AWS resources or services in an account or region. They are designed to protect customers from unintentional spikes in usage or abuse. Granting everyone access to increase AWS service quotas can compromise the security, performance, and cost of your workload. You should follow the principle of least privilege and grant access only to those who need it, and only for the resources and services they need.

Option C is correct because stopping guessing capacity is one of the design principles of the reliability pillar.

Option D is incorrect because designing applications to run in a single Availability Zone is not a design principle of the reliability pillar, nor a best practice for any pillar. An Availability Zone is a physically isolated location within an AWS Region that has independent power, cooling, and network connectivity. Running applications in a single Availability Zone can expose them to failures or disruptions that affect that zone, such as power outages, network issues, or natural disasters. You should design your applications to run in multiple Availability Zones to increase their availability and fault tolerance.

Option E is incorrect because planning to increase AWS service quotas first in a secondary AWS Region is not a design principle of the reliability pillar, nor a best practice for any pillar. A secondary AWS Region is an AWS Region that you use as a backup or disaster recovery site for your primary AWS Region. Increasing AWS service quotas in a secondary AWS Region can incur additional costs and complexity, and may not be necessary if you have enough capacity in your primary AWS Region. You should plan your capacity needs based on your workload requirements and performance goals, and increase AWS service quotas only when needed and in the appropriate regions.

Which design principles are included in reliability pillar of AWS Well-Architected Framework?

Amazon AWS Certified Cloud Practitioner CLF-C02 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified Cloud Practitioner CLF-C02 exam and earn Amazon AWS Certified Cloud Practitioner CLF-C02 certification.