Handing one cloud benefit's definition to another
The wrong answers swap the benefits of the AWS Cloud. Agility is offered for lower prices, economies of scale for fast deployment into several locations, and speed of deployment for scaling capacity down. Each benefit answers one question. Economies of scale explains lower prices from aggregated customer usage. Agility covers provisioning in minutes. Elasticity matches capacity to demand, adding resources at peak and releasing them when demand falls.
See it in a sample questionAssigning a design principle to the wrong Well-Architected pillar
Every wrong option is a genuine design principle placed under the wrong pillar. Least privilege is a security principle, offered here for operational excellence. Right-sizing and a consumption model belong to cost optimisation. Stopping guessing about capacity and testing recovery belong to reliability. Operational excellence means making frequent, small, reversible changes and performing operations as code, so procedures are repeatable and improved.
See it in a sample questionConfusing the Cloud Adoption Framework with Well-Architected
The wrong answers give the two frameworks each other's job. Well-Architected evaluates the design of one workload against pillars such as reliability. The AWS Cloud Adoption Framework guides a whole organisation, grouping capabilities into six perspectives that span business and technology, and it lowers risk by identifying capability gaps and building an action plan. Trusted Advisor and AWS Organizations are offered as adoption guidance, but neither is.
See it in a sample questionChoosing a network service when the link is the bottleneck
When the internet link is too slow, the wrong answers keep the data on the network. Transfer Acceleration still depends on the link, and Direct Connect is a private link built for ongoing traffic. CloudFront serves content out to viewers instead of importing data. A physical device removes the bottleneck: Snowball is shipped to load data, Snowcone suits a few terabytes at a remote site, and Snowmobile is a truck for exabyte-scale moves.
See it in a sample questionTreating a backup or standby as a readable replica
Snapshots, automated backups and weekly exports to Amazon S3 are offered as live copies, but each is a point-in-time or archive copy that lags behind the primary. A Multi-AZ standby exists for resilience and failover and does not normally serve read queries. An Amazon RDS read replica is the continuously updated copy that serves read-only queries and offloads the primary instance.
See it in a sample question