Exam AWS Certified Cloud Practitioner topic 1 question 344 discussion

The design principles of the reliability pillar of the AWS Well-Architected Framework include: Stop guessing capacity: This principle emphasizes the use of autoscaling and elastic architecture to automatically adjust resources based on demand. Make changes in infrastructure by using automation: This principle promotes the use of automation tools to make changes to infrastructure, ensuring consistency, accuracy, and reducing manual errors.

B. Stop guessing capacity. E. Make changes to infrastructure by using automation. https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/design-principles.html

BE is the answer.

should be BE Reliability Automatically recover from failure Test recovery procedures Scale horizontally to increase aggregate workload availability Stop guessing capacity - OK Manage change in automation - OK

B. Stop guessing capacity. E. Make changes to infrastructure by using automation. Design principles that support the reliability pillar are: B. Stop guessing capacity: This principle is about using auto-scaling and monitoring to automatically adjust capacity based on the actual usage of the system. E. Make changes to infrastructure by using automation: This principle is about using tools and scripts to automate the deployment and management of infrastructure, which can reduce human error and improve the ability to respond to changes in demand. Perform operations as code, Adopt serverless architecture whenever possible and Use build and deployment management systems are design principles that support the operational excellence pillar of the AWS Well-Architected Framework.

should be BE

Listed here: https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/design-principles.html

Answer: BE

Stop guessing capacity: A common cause of failure in on-premises workloads is resource saturation, when the demands placed on a workload exceed the capacity of that workload (this is often the objective of denial of service attacks). In the cloud, you can monitor demand and workload utilization, and automate the addition or removal of resources to maintain the optimal level to satisfy demand without over- or under-provisioning. There are still limits, but some quotas can be controlled and others can be managed (see Manage Service Quotas and Constraints). Manage change in automation: Changes to your infrastructure should be made using automation. The changes that need to be managed include changes to the automation, which then can be tracked and reviewed.