Exam AWS Certified Cloud Practitioner topic 1 question 441 discussion

Just had this question in my exam. One of the choices was an ”operation as code”

B. Operational excellence "Perform operations as code: In the cloud, you can apply the same engineering discipline that you use for application code to your entire environment. You can define your entire workload (applications, infrastructure) as code and update it with code. You can implement your operations procedures as code and automate their run process by initiating them in response to events. By performing operations as code, you limit human error and achieve consistent responses to events." https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html

Operational excellence in the cloud: - Perform operations as code: In the cloud, you can apply the same engineering discipline that you use for application code to your entire environment. You can define your entire workload (applications, infrastructure) as code and update it with code. You can implement your operations procedures as code and automate their run process by initiating them in response to events. By performing operations as code, you limit human error and achieve consistent responses to events.

Operational excellence. By performing operations as code, you limit human error and enable consistent responses to events. https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html

B is the answer.

B is correct, keyword: human error

This seems like it could be either B or D. The first part of the question would be B but the second part is definitely D as it goes on about consistency. A company wants to use the AWS Cloud to define its entire infrastructure as code. The company wants to limit human error and activate CONSISTENT responses to events.

B is correct. "define its entire infrastructure as code" it's belong Operational excellence

I think B is correct https://docs.aws.amazon.com/wellarchitected/latest/high-performance-computing-lens/design-principles.html

this is talking about reliability

Make frequent, small, reversible changes: Design workloads to allow components to be updated regularly. Make changes in small increments that can be reversed if they fail (without affecting customers when possible).