Home / SAA-C03 / Objective 2.2

Domain 2: Design Resilient Architectures · 26% of the exam · Full exam outline

2.2 Design highly available and/or fault-tolerant architectures

What this objective covers · 13% of the exam

AWS global infrastructure (for example, Availability Zones, AWS Regions, Amazon Route 53); AWS managed services with appropriate use cases (for example, Amazon Comprehend, Amazon Polly); Basic networking concepts (for example, route tables); Disaster recovery (DR) strategies (for example, backup and restore, pilot light, warm standby, active-active failover, recovery point objective [RPO], recovery time objective [RTO]); Distributed design patterns; Failover strategies; Immutable infrastructure; Load balancing concepts (for example, ALB); Proxy concepts (for example, Amazon RDS Proxy); Service quotas and throttling (for example, how to configure the service quotas for a workload in a standby environment); Storage options and characteristics (for example, durability, replication); Workload visibility (for example, AWS X-Ray); Determining automation strategies to ensure infrastructure integrity; Determining the AWS services required to provide a highly available and/or fault-tolerant architecture across AWS Regions or Availability Zones; Identifying metrics based on business requirements to deliver a highly available solution; Implementing designs to mitigate single points of failure; Implementing strategies to ensure the durability and availability of data (for example, backups); Selecting an appropriate DR strategy to meet business requirements; Using AWS services that improve the reliability of legacy applications and applications not built for the cloud (for example, when application changes are not possible); Using purpose-built AWS services for workloads

Practice questions

Question 1easy

An operations team patches its web servers by logging in over SSH and running updates on each running instance. Over time the servers have drifted apart in configuration. Which change follows an immutable infrastructure model?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Running the script everywhere at once makes changes more uniform, but it is still an in-place modification of running servers, the exact anti-pattern immutable infrastructure rules out.

Adding capacity changes how many servers exist, not how they are changed. The new servers would be patched over SSH like the rest, so nothing about the model becomes immutable.

Immutable infrastructure forbids in-place updates, patches and configuration changes on production resources. A new, updated set of resources is deployed and traffic moves to it, which also removes the drift because every server comes from the same known image.

Snapshots give a point-in-time copy to fall back on, which reduces risk, but the servers are still changed in place and keep drifting. It protects against a bad patch rather than removing the practice causing drift.

Question 2easy

An order API calls three internal microservices, a database, and an external payment API. Some orders take several seconds, and engineers need to see, for an individual slow request, which downstream call added the delay. Which AWS service provides this view?

Included in Master: master every domain.See plans