You save $69.98
AZ-305 Premium Bundle
- Premium File 382 Questions & Answers
- Last Update: Nov 20, 2026
- Training Course 87 Lectures
- Study Guide 933 Pages
You save $69.98
The acceptance criterion for Blob ZRS availability comes from this issue: A business-critical file repository must survive an availability-zone outage without a regional failover. Which measured outcome is the strongest proof?
ZRS synchronously replicates data across primary-region zones. Confirm using the measurable result: Reading and writing a test blob continues while one zone is unavailable.
This result tests how an AKS service behaves when one availability zone fails and workloads recover onto eligible healthy-zone nodes. It does not establish whether Azure Blob Storage maintains read/write availability under zonal failure; that requires the distinct ZRS storage test in option C.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. The distinguishing check is: Reading and writing a test blob continues while one zone is unavailable.
Read regions bring replicas closer to users without inherently adding multi-write semantics. The offered observation would demonstrate Cosmos multi-region reads: Read latency declines for remote users while sessions observe selected consistency. The current validation is different: Reading and writing a test blob continues while one zone is unavailable.
Architecture review: Blob hot/cool/cold and Blob inventory. Requirement A: A log archive sees frequent access for a month and rare access afterward. Requirement B: Operations needs a weekly manifest of millions of blobs with properties and access tiers. Which complete two-part proposal satisfies both constraints?
For requirement A, tiering trades storage price against access and retrieval cost based on usage. For requirement B, blob Inventory produces scheduled object inventories without crawling each object individually. Verify both independently: Old eligible blobs transition to the intended tier and remain retrievable; The manifest lists the expected blob properties in the configured destination.
The mismatched half is Cosmos DB NoSQL; Blob inventory instead needs: Configure Azure Storage Blob Inventory reports.
This combines Storage service endpoints and Cosmos DB NoSQL, which do not satisfy the distinct requirements for Blob hot/cool/cold and Blob inventory.
The option covers one requirement but substitutes Storage service endpoints for Blob hot/cool/cold. The missing acceptance result is: Old eligible blobs transition to the intended tier and remain retrievable.
A read-heavy catalog repeatedly queries relational data for identical frequently accessed results. Identify the most suitable implementation for an outcome where cache hits reduce SQL query volume and expired entries refresh correctly.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. The selected architecture is use a managed Azure Redis-compatible cache with invalidation and TTL design; confirm the result by checking that cache hits reduce SQL query volume and expired entries refresh correctly.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. It does not solve the specified Azure Cache for Redis condition.
Blob change feed records changes to blob objects for downstream processing. The current need is: A read-heavy catalog repeatedly queries relational data for identical frequently accessed results.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. That is useful for Cosmos autoscale (An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful). It does not meet the current Azure Cache for Redis requirement: A read-heavy catalog repeatedly queries relational data for identical frequently accessed results.
For the Container Apps microservice requirement, the proposed architecture uses: Use Azure Container Apps with suitable ingress scaling and revision settings. Why does that design fit?
Container Apps provides managed container hosting and microservice scale with KEDA capabilities. It is material here because several HTTP container services need autoscaling and revisions without management of a full Kubernetes control plane.
Encryption sets connect managed disk encryption to customer-owned keys. Container Apps provides managed container hosting and microservice scale with KEDA capabilities.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. Container Apps provides managed container hosting and microservice scale with KEDA capabilities.
Blue-green deployment preserves a prior known-good instance while testing a replacement. It belongs to App deployment blue-green. The stated architecture instead relies on: Container Apps provides managed container hosting and microservice scale with KEDA capabilities.
Architecture review: Policy remediation and Deployment drift. Requirement A: Existing resources are missing diagnostic settings despite new deployments receiving automatic configuration. Requirement B: A production app's manually changed resource settings diverge from the approved IaC template. Which complete two-part proposal satisfies both constraints?
For requirement A, deployIfNotExists requires remediation for already deployed resources where appropriate. For requirement B, Azure deployment what-if previews resource changes before applying a template. Verify both independently: The noncompliant existing resources receive the required settings without manual per-resource editing; The change report identifies manual drift and approved deployment restores the intended state.
The option covers one requirement but substitutes Resource naming governance for Policy remediation. The missing acceptance result is: The noncompliant existing resources receive the required settings without manual per-resource editing.
DeployIfNotExists requires remediation for already deployed resources where appropriate. Azure deployment what-if previews resource changes before applying a template. The proposed steps (adopt a standardized resource naming and tagging strategy in landing-zone governance; adopt an Azure landing-zone architecture following the Cloud Adoption Framework) address other capabilities instead of this required pair.
The mismatched half is Landing zones; Deployment drift instead needs: Use a what-if deployment comparison and controlled remediation for the declared configuration.
Architecture review: Private endpoint and DNS private zones. Requirement A: A storage service must have an address in a VNet and reject access from the public internet. Requirement B: A service private endpoint resolves to a public address from a peered spoke VNet. Which complete two-part proposal satisfies both constraints?
For requirement A, private endpoints attach supported PaaS access to a private IP and require DNS resolution. For requirement B, private DNS zone links determine name resolution for VNets that consume private endpoints. Verify both independently: The data source resolves to a VNet private address and public access is denied; A lookup from the spoke resolves the service FQDN to the intended private IP.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. Private DNS zone links determine name resolution for VNets that consume private endpoints. The proposed steps (use Network Watcher connection troubleshoot and IP flow verify where supported; evaluate Azure Virtual WAN secured virtual hubs and routing intent) address other capabilities instead of this required pair.
The mismatched half is Virtual WAN global hubs; DNS private zones instead needs: Link the appropriate Azure Private DNS zone and configure private endpoint DNS records.
The first step implements Network Watcher diagnosis instead of Private endpoint. The necessary change is to use Azure Private Link private endpoint with private DNS and disable public access.
A rollout addressing Logic Apps connector workflow has reached acceptance testing. The original problem was: A business process requires approvals plus connectors for Microsoft 365 and a SaaS ticketing system. Which finding verifies its resolution?
Logic Apps offers managed integration workflows and prebuilt service connectors. Confirm using the measurable result: An approved request creates the expected ticket and notifies the right mailbox.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The Front Door rules engine test checks requests to the deprecated path redirect and supported responses include the configured header; the relevant outcome is An approved request creates the expected ticket and notifies the right mailbox.
Event Grid distributes discrete source events to configured subscribers. The offered observation would demonstrate Event Grid notification: Only event handlers matching the subject filter are invoked for the test upload. The current validation is different: An approved request creates the expected ticket and notifies the right mailbox.
Edge caching reduces origin load and latency for eligible cacheable content. Those observations validate Azure Front Door caching. They do not establish the required Logic Apps connector workflow result: An approved request creates the expected ticket and notifies the right mailbox.
Architecture review: SQL long-term recovery and SQL geo-restore. Requirement A: A legal obligation requires recovery of relational records from a backup taken five years ago. Requirement B: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Which complete two-part proposal satisfies both constraints?
For requirement A, LTR retains selected full backups over years rather than only the standard short PITR window. For requirement B, geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. Verify both independently: A designated five-year backup remains listed and can restore a compliant copy; A region-loss exercise recovers a database from the latest supported geo backup.
The first step implements Blob vaulted backup instead of SQL long-term recovery. The necessary change is to configure Azure SQL long-term retention for the required backup schedule.
Both proposed halves address other use cases: Blob vaulted backup and PostgreSQL PITR. The requested pair is SQL long-term recovery and SQL geo-restore.
The mismatched half is PostgreSQL PITR; SQL geo-restore instead needs: Plan Azure SQL geo-restore with acceptable recovery objectives and backup redundancy.
The target environment adopts this approach for Blob HNS namespace: Enable hierarchical namespace and use Azure Data Lake Storage Gen2 capabilities. What property makes it suitable?
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. It is material here because analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage.
Blob change feed records changes to blob objects for downstream processing. ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. It belongs to Blob user-delegation SAS. The stated architecture instead relies on: ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage.
Blob Inventory produces scheduled object inventories without crawling each object individually. ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage.
An architect must sign off on Synapse dedicated SQL. The business problem is: A large enterprise data warehouse requires predictable reserved compute for repeatable analytic SQL workloads. What observed test result provides valid evidence?
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Confirm using the measurable result: The fact-table join finishes within measured performance goals under the planned workload.
Stream Analytics supports SQL-like processing over streaming sources with time windows. The Stream Analytics window test checks an expected count is emitted for each completed five-minute event window; the relevant outcome is The fact-table join finishes within measured performance goals under the planned workload.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. The offered observation would demonstrate Service Bus ordering: A poison message moves to the dead-letter queue while ordered session items retain their sequence. The current validation is different: The fact-table join finishes within measured performance goals under the planned workload.
Mapping data flows transform data on managed Spark compute from graphical mappings. Those observations validate ADF mapping data flow. They do not establish the required Synapse dedicated SQL result: The fact-table join finishes within measured performance goals under the planned workload.
The acceptance criterion for Policy exclusion scope comes from this issue: One application needs a carefully controlled exception to a management group policy. Which measured outcome is the strongest proof?
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. Confirm using the measurable result: Only the approved application scope avoids the specified policy effect.
Custom role actions can grant specific management operations without broad Contributor rights. The RBAC custom role test checks the operator restarts an approved service and cannot modify resource access assignments; the relevant outcome is Only the approved application scope avoids the specified policy effect.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. The offered observation would demonstrate Managed governance dashboards: An auditor filters noncompliant resources by subscription and policy assignment. The current validation is different: Only the approved application scope avoids the specified policy effect.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Those observations validate Defender compliance. They do not establish the required Policy exclusion scope result: Only the approved application scope avoids the specified policy effect.
Please check your mailbox for a message from support@examlabs.com and follow the directions.