The server vouches for itself. No password in a config file. No secret sitting where it can leak.
This path trains you to evaluate business requirements, identity choices, landing zones, storage decisions, and integration patterns the way an architect should: through tradeoffs, constraints, resilience, and cost.
The server vouches for itself. No password in a config file. No secret sitting where it can leak.
This is the city plan before the buildings go up. Connectivity, governance, identity, and management are designed first.
Not every app needs the exact same database guarantees. Architecture is knowing what the workload actually needs and paying only for that.
Entra ID choices, hybrid identity, external identities, PIM, management groups, policy inheritance, and enterprise landing zones.
Azure SQL Database versus Managed Instance versus SQL on VM, Cosmos DB models, Data Lake, Synapse, and integration tradeoffs.
Data Factory, messaging, API patterns, managed identities, and service choices based on operational needs.
Architecting for scale, recovery, governance, and cost control without overengineering the environment.
The source material defines the early modules directly. The remaining modules extend the same exam-driven design logic across the rest of the architect scope.
Use Microsoft Learn paths for architecture scenarios, identity design, and governance at scale.
Practice choosing services against requirements: latency, compatibility, global scale, compliance, and recovery targets.
Prototype management groups, policy assignments, and reference architectures in a sandbox tenant before production.
If your next move is cloud architect, lead engineer, or platform design, AZ-305 is the cert path that forces you to reason through requirements instead of memorizing feature names.
Architect expert pathway
View options