Know why, not just what.
IT certification practice questions with a verified answer and a full explanation on every single question — not a crowd-voted guess and a paywall on the reasoning.
Verified answers
Every answer is checked by a subject-matter expert and cross-referenced against current vendor documentation — never just a crowd vote.
Explanation-first
You see why the correct answer is correct, and why each other option isn't, by default. No extra click, no paywall on the reasoning.
Adaptive study
Spaced repetition and weak-area tracking replace the flat, static question list — so practice time goes where it actually helps.
A real question from our AWS Solutions Architect Associate bank
Objective 2.1 · Design resilient architectures
A company runs a web application on a single EC2 instance behind no load balancer. The application must tolerate the failure of an entire Availability Zone with minimal downtime. Which change best meets this requirement?
- AMove the instance to a larger instance type in the same Availability Zone.
- BDeploy an Auto Scaling group across multiple Availability Zones behind an Application Load Balancer.
- CTake a daily AMI snapshot and restore manually if the zone fails.
- DEnable EC2 instance recovery within the same Availability Zone.
Why this is correct
An Auto Scaling group spanning multiple Availability Zones, fronted by an Application Load Balancer, automatically routes traffic away from a failed zone and replaces lost capacity — this is the standard resilience pattern for AZ-level failure.
Why the others aren't
A) A bigger instance in the same AZ doesn't survive an AZ failure. C) Manual restore from a daily AMI causes significant downtime and data loss risk, and doesn't meet 'minimal downtime'. D) Instance recovery only handles hardware failure of the same host, not a full zone outage.
Source: AWS Well-Architected Framework — Reliability PillarSimple, transparent pricing
Every limit and every dollar is stated up front — no device caps or refund fine print discovered after you've paid.
See pricing