All of the options are valid principles of the AWS Well-architected framework. However, the question is specific to the "Reliability Pillar." Here is the breakdown of each option:
A. Perform operations as code --> Operational Excellence
B. Enable traceability --> Security
C. Automatically scale to meet demand --> Reliability
D. Deploy resources globally to improve response time --> Performance Efficiency
E. Automatically recover from failure --> Reliability
So correct answers are C & E.
B&E B. Enable traceability: This principle focuses on ensuring that you have the ability to trace and investigate actions and changes made in your environment. It includes logging and monitoring mechanisms, as well as the ability to track changes, access logs, and analyze data for troubleshooting and auditing purposes.
It is actually A and E.
https://wa.aws.amazon.com/wat.pillar.reliability.en.html
There are five design principles for reliability in the cloud:
Automatically recover from failure
Test recovery procedures
Scale horizontally to increase aggregate workload availability
Stop guessing capacity
Manage change in automation
C. Automatically scale to meet demand and E. Automatically recover from failure are the two design principles that support the reliability pillar of the AWS Well-Architected Framework.
The reliability pillar of the AWS Well-Architected Framework focuses on the ability of a system to recover from failures, as well as to prevent failures from occurring. Here are the explanations of the two design principles:
C. Automatically scale to meet demand: This design principle ensures that the system can handle increases in traffic and demand without being overwhelmed. By automatically scaling resources in response to changes in demand, the system can maintain reliability and performance.
E. Automatically recover from failure: This design principle ensures that the system can recover quickly and automatically from failures. By automating the recovery process, the system can reduce downtime and maintain availability for users.
Automatically recover from failure: By monitoring a workload for key performance indicators (KPIs), you can trigger automation when a threshold is breached. These KPIs should be a measure of business value, not of the technical aspects of the operation of the service. This allows for automatic notification and tracking of failures, and for automated recovery processes that work around or repair the failure. With more sophisticated automation, it’s possible to anticipate and remediate failures before they occur.
Scale horizontally to increase aggregate workload availability: Replace one large resource with multiple small resources to reduce the impact of a single failure on the overall workload. Distribute requests across multiple, smaller resources to ensure that they don’t share a common point of failure.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
isaphiltrick
1 year, 6 months agoPranava_GCP
1 year, 9 months agomohamedmesbah
1 year, 9 months agodarn
2 years agoAmycert
2 years, 1 month agolinux_admin
2 years, 1 month agocexars
2 years, 3 months agoSaif93
2 years, 3 months agoEman_Negm
2 years, 3 months agoMeeso
2 years, 3 months agoMeeso
2 years, 3 months agoKelland
2 years, 3 months agoPatos
2 years, 3 months agoall4one
2 years, 3 months ago