Where logs land and how long they stay
Routing logs to the systems that consume them
Choosing what gets watched and who gets woken
© 2026 Dometrain. All rights reserved.
Requirement-driven AZ-305 design questions across all four skill areas, each lesson teaching the material before it grades you.
AZ-305 does not ask you to name a service. It hands you a set of requirements and asks which Azure design satisfies them: the storage option that meets a stated durability target, the identity control that meets a stated access rule, the recovery plan that meets a stated recovery point, the network shape that keeps a regulated flow off the public internet. This course is built the same way. Every lesson is a graded question set covering one part of the published exam outline, and every one of them opens with the teaching text you need to answer it. Nothing is assessed that the lesson, or a lesson before it, has not already taught. After you answer, every option is explained, chosen or not, so a wrong pick tells you which misconception you were carrying rather than simply marking you down. Chapter sizes track the exam’s own weighting across identity and governance, data storage, business continuity, and infrastructure design, so the time you spend maps onto the marks that are actually available. Questions state a constraint and ask for a recommendation, which is the shape the real exam uses and the shape the job uses. You will pick workspace layouts and retention plans, sign-in methods and role scopes, relational and non-relational stores, compute and container hosts, migration strategies, network edges, backup designs, and availability topologies, and in each case you will be able to say what the rejected options fail.
