Microsoft Azure & FabricLive · 108 questions · 12 notes

AZ-305: Designing Microsoft Azure Infrastructure Solutions

Free practice exam, study notes with architecture diagrams and the official blueprint for Designing Microsoft Azure Infrastructure Solutions.

Passing score
700 / 1000
Domains
4
Exam code
AZ-305

Official AZ-305 exam blueprint

Domains and weights from Microsoft Azure & Fabric's exam guide.

DomainWeight
Design identity, governance, and monitoring solutions25–30%
Design data storage solutions20–25%
Design business continuity solutions15–20%
Design infrastructure solutions30–35%

Free AZ-305 sample questions

The first questions of the free diagnostic. Pick your answer, then check it. Why every option is right or wrong, and the What-If twist, open in the workspace.

  1. Question 1 · Design authentication and authorization solutions

    A manufacturer is moving staff sign-in to Microsoft Entra ID for Microsoft 365. Its security policy requires that on-premises sign-in hours and account expiration are enforced at every cloud sign-in, and the company wants to avoid running an AD FS farm. Which hybrid authentication method meets the policy?
    1. APass-through authentication
    2. BPassword hash synchronization
    3. CFederation with AD FS
    4. DCloud-only accounts with no synchronization
    Check the answer

    Answer: A. PTA checks every sign-in on-premises; PHS works without on-premises servers and enables leaked-credential detection.

    Official docs: Microsoft Learn: Choose the right authentication method for your Microsoft Entra hybrid identity solution
    Unlock Full 4-Option Autopsy & What-If Twist in Workspace
  2. Question 2 · Design governance

    An enterprise is setting up Azure landing zones for 60 subscriptions. Shared networking and identity platform resources need their own guardrails, application subscriptions split into internal-only and internet-facing workloads, and experiments must stay isolated from production policy. How should the management group hierarchy be structured?
    1. AA deep tree that mirrors every department and country
    2. BOne management group for each subscription
    3. CEvery subscription directly under the tenant root group
    4. DPlatform, landing zones with corp and online children, sandbox and decommissioned groups under an intermediate root
    Check the answer

    Answer: D. Landing zone management groups follow workload archetypes, so policies apply once and inherit downward.

    Official docs: Microsoft Learn: What is an Azure landing zone?
    Unlock Full 4-Option Autopsy & What-If Twist in Workspace
  3. Question 3 · Design solutions for logging and monitoring

    A retailer with one Microsoft Entra tenant runs workloads in the United States and the European Union. Regulators require EU monitoring data to stay in the EU, while US data has no location requirement, and the operations team wants as few Log Analytics workspaces as possible to keep cross-workspace queries simple. Today every resource sends data to this workspace:

    Bicep
    resource law 'Microsoft.OperationalInsights/workspaces@2023-09-01' = {
      name: 'law-global'
      location: 'eastus'
      properties: { retentionInDays: 90, sku: { name: 'PerGB2018' } }
    }

    Which workspace design should the architect recommend?

    1. AOne global workspace in a US region for all data
    2. BOne workspace per subscription
    3. COne workspace in an EU region for EU resources and one workspace for everything else
    4. DOne workspace per resource group
    Check the answer

    Answer: C. Start with one Log Analytics workspace and add more only for criteria such as residency, tenants, ownership or retention.

    Official docs: Microsoft Learn: Design a Log Analytics workspace architecture
    Unlock Full 4-Option Autopsy & What-If Twist in Workspace
Answer all 10 free AZ-305 questions

AZ-305 study notes: key concepts

What each note covers. The full notes, with summaries, examples and memory hooks, open with a free account.

Architecture flow · Design solutions for logging and monitoring

From Azure resources to monitoring consumers
  1. 1Sources

    Azure resources platform logs

    • leads to Diagnostic settings

    VMs with Azure Monitor Agent

    • leads to Data collection rules
  2. 2Routing

    Diagnostic settings

    • leads to Log Analytics workspace
    • leads to Immutable storage archive
    • leads to Event Hubs stream

    Data collection rules

    • leads to Log Analytics workspace
  3. 3Destinations

    Log Analytics workspace

    • leads to Microsoft Sentinel and alerts

    Immutable storage archive

    Event Hubs stream

    • leads to Third-party SIEM
  4. 4Consumers

    Microsoft Sentinel and alerts

    Third-party SIEM

Drawn fromMicrosoft Learn: Design a Log Analytics workspace architecture

Design solutions for logging and monitoring

  • Start with a single Log Analytics workspace and create more only for residency, separate tenants, data ownership, split billing or retention that differs for the same tables.
  • Resource-context RBAC lets users read logs only for resources they can already access, and table-level RBAC grants or denies specific tables such as security data.
  • Table plans trade features for price: Analytics for monitoring and alerts, Basic for troubleshooting, Auxiliary for cheap long-term verbose data with aggregated queries.
  • Diagnostic settings route platform logs to a workspace, a storage account and an event hub at once, and regional resources need regional storage and event hub destinations.
  • Commitment tiers discount ingestion per workspace, so combining operational and security data in one workspace can reach a cheaper tier than two separate ones.

Design authentication and authorization solutions

  • Password hash synchronization authenticates in Microsoft Entra ID without on-premises servers in the sign-in path and is required for leaked-credential detection in Identity Protection.
  • Pass-through authentication checks each sign-in against on-premises Active Directory, so on-premises sign-in hours and account expiration apply without running an AD FS farm.
  • Privileged Identity Management makes users eligible for roles that they activate just in time with approval and an expiry, replacing standing privileged access.
  • User-assigned managed identities exist independently of any resource, so one identity granted access once can serve many apps and survive their redeployment.
  • Key Vault Standard uses software keys, Premium adds HSM-protected keys in a shared service, and Managed HSM gives single-tenant validated HSM pools.

Design governance

  • Assign policies and roles at management groups so every subscription below inherits them, grouping subscriptions by workload archetype rather than by the organization chart.
  • Deny blocks non-compliant requests, while modify and deployIfNotExists change resources through remediation tasks that run as the assignment's managed identity with granted roles.
  • An enforcementMode of DoNotEnforce evaluates compliance without enforcing effects, so brownfield subscriptions can see their gaps before guardrails start blocking deployments.
  • Policy exemptions waive an assignment for a scope, and an expiresOn date ends the waiver automatically so the resources are evaluated normally again.
  • Access reviews ask owners to recertify memberships on a schedule and can remove access automatically, while access packages handle requests, approvals and expiry.

Design data storage solutions for relational data

  • Azure SQL Managed Instance keeps SQL Server Agent jobs, cross-database queries and CLR in a managed service, so instance-dependent estates migrate without rewrites.
  • Business Critical runs on local SSD with built-in replicas, including a readable replica reached with ApplicationIntent=ReadOnly, and supports a zone-redundant configuration.
  • Hyperscale scales storage well beyond other tiers, restores quickly from file snapshots regardless of size, and adds named replicas for independently scaled read workloads.
  • Always Encrypted encrypts sensitive columns on the client so database administrators never see plaintext, while dynamic data masking only obfuscates results for non-privileged users.
  • Failover groups replicate databases to another region behind read-write and read-only listener endpoints, so apps don't change connection strings after a geo-failover.

Design data storage solutions for semi-structured and unstructured data

  • Session consistency guarantees read-your-writes within a client session, which suits per-user data like carts at lower latency and request unit cost than stronger levels.
  • A high-cardinality partition key such as a customer ID spreads requests across partitions, while a low-cardinality key like country creates hot partitions that throttle.
  • Lifecycle management rules move blobs to cool, cold or archive tiers by age, and archived blobs must be rehydrated, which can take hours, before they can be read.
  • Azure Data Lake Storage adds a hierarchical namespace to Blob Storage, giving real directories, POSIX-style ACLs and atomic directory renames for analytics engines.
  • Locked time-based retention keeps blobs immutable for a fixed period that nobody can shorten, while legal holds keep data immutable until someone explicitly clears them.

Design data integration

  • A self-hosted integration runtime installed in the private network makes outbound connections to Data Factory, so it reaches on-premises sources without opening inbound firewall ports.
  • The Azure-SSIS integration runtime runs existing SSIS packages inside Data Factory, which lets a large SSIS estate move to Azure with little or no rewriting.
  • A linked service's connectVia property chooses the integration runtime, so an on-premises source must point at the self-hosted runtime rather than the default Azure runtime.
  • Use the factory's managed identity where targets accept Microsoft Entra authentication, and Key Vault references for passwords, keeping every secret out of pipeline definitions.
  • Azure Data Explorer ingests streaming telemetry and runs KQL time-series queries quickly over billions of rows, a better fit than relational databases for device data.
Read the full AZ-305 study notes

AZ-305 FAQ

What is the passing score for AZ-305?

The passing score for Designing Microsoft Azure Infrastructure Solutions is 700 / 1000.

Which domains does AZ-305 cover?

The official exam guide lists 4 domains: Design identity, governance, and monitoring solutions (25–30%); Design data storage solutions (20–25%); Design business continuity solutions (15–20%); Design infrastructure solutions (30–35%).

Is there a free AZ-305 practice test?

Yes. Gyan AI's free diagnostic is 10 AZ-305 questions with no sign-up, each with an explanation for every option and a link to the official documentation. A free account unlocks the full question set and study notes.

Are these the real AZ-305 exam questions?

No. Real exam content is confidential under vendor exam agreements, and using leaked "dumps" can get a certification revoked. Gyan AI questions are original and written to the published skills outline.