AZ-305 Practice — Timed Sets & Architecture Mocks

Open the practice app for AZ-305. Start with domain-focused drills, then run full architecture-style mocks. Mobile-friendly and aligned to Microsoft’s blueprint.

Interactive Practice Center

Start a practice session for AZ-305: Designing Microsoft Azure Infrastructure Solutions below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.

Open Full App in a New Tab

This embedded web app includes a generous freemium mode, with up to about 400 practice questions available for each supported exam so you can gauge your readiness before upgrading.

Prefer to practice on your phone or tablet? Download the Mastery Cloud – AWS, Azure, GCP & CompTIA exam prep app for iOS or Mastery Cloud app on Google Play (Android) and sign in with the same Mastery account to unlock your subscription on the web and continue your sessions on a laptop or desktop browser.

Tip: AZ-305 is about design justification. In review mode, write a one-line “why” for every miss (e.g., “needs private access”, “needs multi-region failover”, “needs message ordering”, “prefers managed PaaS”).


Suggested progression

  1. Domain drills (daily): 2× 20–30 question sets focused on one domain.
  2. Mixed sets (alternate days): 1× 35–45 questions combining 2–3 domains.
  3. Full mocks (final 10 days): 2–3 complete exams; review every miss and rebuild weak domains.

Timeboxing

  • Domain set: ~35–50 minutes
  • Mixed set: ~60–75 minutes
  • Full mock: ~120 minutes

Fast remediation patterns (common weak spots)

  • Ingress choice: Front Door (global edge) vs App Gateway (regional L7/WAF) vs Load Balancer (L4) vs Traffic Manager (DNS).
  • Private access: Private Endpoint + Private DNS for PaaS; don’t “forget DNS.”
  • Relational pickers: SQL DB vs Managed Instance vs SQL VM based on compatibility + ops responsibility.
  • RTO/RPO: backups ≠ DR; pick ASR/geo-replication when the RTO/RPO demands it.
  • Governance: management groups + policy initiatives + tagging/budgets for scale, not per-resource manual controls.

What to pair with practice