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
Operators must turn a feature on for a pilot group without rebuilding application binaries. The acceptance test is: Pilot users see the feature after refresh and others retain the previous behavior. Which design recommendation best satisfies both?
App Configuration centralizes feature settings; secrets should remain in Key Vault. The selected architecture is store nonsecret feature flags in Azure App Configuration with app-side refresh; confirm the result by checking that pilot users see the feature after refresh and others retain the previous behavior.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The relevant requirement is: Operators must turn a feature on for a pilot group without rebuilding application binaries.
Edge content distribution can cache static resources near users. It does not solve the specified App Configuration feature flags condition.
Asynchronous projections can lag writes and need clear read-after-write expectations. That is useful for Eventual consistency UX (An order service writes asynchronously into a read model and users momentarily see old data). It does not meet the current App Configuration feature flags requirement: Operators must turn a feature on for a pilot group without rebuilding application binaries.
The Key Vault app secrets review proposes: Reference Key Vault secrets using workload identity from the application. Which Azure behavior is the technical justification for this decision?
Central secret retrieval separates sensitive credentials from source and build artifacts. It is material here because a deployed API must rotate an external vendor credential without checking a new secret into Git.
At-least-once message delivery requires application logic to deduplicate business side effects. Central secret retrieval separates sensitive credentials from source and build artifacts.
APIM can enforce per-client API consumption controls before requests reach backends. It belongs to APIM rate limiting. The stated architecture instead relies on: Central secret retrieval separates sensitive credentials from source and build artifacts.
An API gateway can broker external requests to private backends without direct public backend access. That statement describes API private backends, while the question asks how Key Vault app secrets works: Central secret retrieval separates sensitive credentials from source and build artifacts.
A branch file server should retain local caching while most data moves to Azure Files. A deployment must satisfy this operational criterion: Frequently used files remain locally available and cold files tier to cloud. Which plan is appropriate?
File Sync preserves local namespace access while synchronizing with Azure file shares. The selected architecture is use Azure File Sync with suitable cloud tiering and server endpoints; confirm the result by checking that frequently used files remain locally available and cold files tier to cloud.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. It does not solve the specified Azure File Sync condition.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. Its design target is Physical server migration. The stated requirement instead concerns: A branch file server should retain local caching while most data moves to Azure Files.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. The relevant requirement is: A branch file server should retain local caching while most data moves to Azure Files.
To validate the Eventual consistency UX deployment, reviewers revisit this operational need: An order service writes asynchronously into a read model and users momentarily see old data. What result confirms it was met?
Asynchronous projections can lag writes and need clear read-after-write expectations. Confirm using the measurable result: The UI shows pending status until the read model catches up without duplicate updates.
Event Grid distributes discrete source events to configured subscribers. The distinguishing check is: The UI shows pending status until the read model catches up without duplicate updates.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. The offered observation would demonstrate Durable Functions orchestration: Restarting a worker does not restart already completed business steps. The current validation is different: The UI shows pending status until the read model catches up without duplicate updates.
Shared session state survives an individual stateless app worker replacement. Those observations validate Azure Cache for Redis session. They do not establish the required Eventual consistency UX result: The UI shows pending status until the read model catches up without duplicate updates.
Demand for a stateless API swings by 10x and manual provisioning causes downtime. Which Azure architecture would most directly achieve the required result: Traffic spikes scale instances out and scale-in does not lose persistent session state?
VMSS can add or remove similarly configured VM instances based on supported signals. The selected architecture is use Virtual Machine Scale Sets with autoscale rules and a stateless design; confirm the result by checking that traffic spikes scale instances out and scale-in does not lose persistent session state.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. Its design target is App Service zone redundancy. The stated requirement instead concerns: Demand for a stateless API swings by 10x and manual provisioning causes downtime.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. It does not solve the specified VM scale set autoscaling condition.
ZRS synchronously replicates data across primary-region zones. That is useful for Blob ZRS availability (A business-critical file repository must survive an availability-zone outage without a regional failover). It does not meet the current VM scale set autoscaling requirement: Demand for a stateless API swings by 10x and manual provisioning causes downtime.
For the ADF mapping data flow requirement, the proposed architecture uses: Use Azure Data Factory mapping data flows with appropriate execution sizing. Why does that design fit?
Mapping data flows transform data on managed Spark compute from graphical mappings. It is material here because an analyst wants a GUI-defined transformation over millions of input rows without maintaining Spark scripts.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Mapping data flows transform data on managed Spark compute from graphical mappings.
Partner event integration routes supported third-party event types without custom polling. Mapping data flows transform data on managed Spark compute from graphical mappings.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. It belongs to Databricks Delta Lake. The stated architecture instead relies on: Mapping data flows transform data on managed Spark compute from graphical mappings.
A solution must address both App deployment blue-green and App Service web. First requirement: A mission-critical API needs a low-risk deployment with rapid rollback of application code. Second requirement: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Select TWO recommendations that meet these independent needs.
For the App Service web half of this design, App Service manages web hosting and supports deployment slots on eligible plans. Check: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts. The other half concerns App deployment blue-green.
For the App deployment blue-green half of this two-part design, blue-green deployment preserves a prior known-good instance while testing a replacement. Verify: A failed health check returns traffic to the prior application version. The other half concerns App Service web.
Durable Functions manages stateful workflows over serverless function executions. The corresponding task is Azure Functions durable workflow: A workflow waits hours between steps while retaining orchestration state through restarts. It is not one of the two requested controls (App deployment blue-green and App Service web).
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. This alternative solves AKS full Kubernetes, while the question separately requires App deployment blue-green and App Service web.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. The corresponding task is Memory optimized VM: An in-memory analytics engine repeatedly pages memory on a standard VM size. It is not one of the two requested controls (App deployment blue-green and App Service web).
Existing resources are missing diagnostic settings despite new deployments receiving automatic configuration. An architecture board will approve a solution only if this outcome is demonstrated: The noncompliant existing resources receive the required settings without manual per-resource editing. What should be selected?
DeployIfNotExists requires remediation for already deployed resources where appropriate. The selected architecture is create a policy remediation task with suitable identity permissions for supported deployIfNotExists rules; confirm the result by checking that the noncompliant existing resources receive the required settings without manual per-resource editing.
Landing zones combine platform foundations with repeatable application subscription governance. That is useful for Landing zones (A growing organization needs repeatable subscriptions with identity, network and governance baselines). It does not meet the current Policy remediation requirement: Existing resources are missing diagnostic settings despite new deployments receiving automatic configuration.
Modify effects can update eligible metadata and require the required remediation permissions. Its design target is Inherited tagging. The stated requirement instead concerns: Existing resources are missing diagnostic settings despite new deployments receiving automatic configuration.
Policy evaluates resource deployment properties and rejects noncompliant regions. It does not solve the specified Policy remediation condition.
Architecture review: API private backends and Application Gateway path routing. Requirement A: An internet-facing API gateway must call a private service not directly exposed to the internet. Requirement B: One regional HTTPS endpoint needs /api requests routed to API pods and /shop to a web tier. Which complete two-part proposal satisfies both constraints?
For requirement A, an API gateway can broker external requests to private backends without direct public backend access. For requirement B, application Gateway provides application-aware path routing rather than basic L4 forwarding. Verify both independently: External callers only reach the backend through the controlled APIM endpoint; Requests to each path arrive at the correct healthy backend pool.
The mismatched half is App Configuration feature flags; Application Gateway path routing instead needs: Use Application Gateway URL-path-based routing with TLS and health probes.
Both proposed halves address other use cases: Key Vault app secrets and App Configuration feature flags. The requested pair is API private backends and Application Gateway path routing.
One action is correct. The other targets Key Vault app secrets, leaving API private backends unsolved. Its necessary action is: Use an APIM networking tier/mode and private backend connectivity supported by the chosen plan.
Architecture rationale review—Refactor monolith: Plan an incremental refactor into bounded services with asynchronous integration. Which explanation accurately distinguishes this capability?
Refactoring changes application structure and decouples independent workloads. It is material here because an app must separate independent high-scale workloads and use managed messaging.
File Sync preserves local namespace access while synchronizing with Azure file shares. Refactoring changes application structure and decouples independent workloads.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Refactoring changes application structure and decouples independent workloads.
Hybrid reachability depends on both routing and security decisions in the destination VNet. It belongs to Hybrid route validation. The stated architecture instead relies on: Refactoring changes application structure and decouples independent workloads.
Architecture rationale review—Recovery time objective: Choose a standby and failover design measured against the thirty-minute RTO. Which explanation accurately distinguishes this capability?
RTO is the maximum acceptable restoration duration, not the amount of lost data. It is material here because a payment system must resume in thirty minutes after a regional outage.
Soft delete retains recoverable protected backup data after deletion for a configured interval. It belongs to Backup soft delete. The stated architecture instead relies on: RTO is the maximum acceptable restoration duration, not the amount of lost data.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. That statement describes SQL database PITR, while the question asks how Recovery time objective works: RTO is the maximum acceptable restoration duration, not the amount of lost data.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. RTO is the maximum acceptable restoration duration, not the amount of lost data.
Please check your mailbox for a message from support@examlabs.com and follow the directions.