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
For the Blob user-delegation SAS requirement, the proposed architecture uses: Issue a scoped user-delegation SAS with the minimum permissions and expiry. Why does that design fit?
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. It is material here because a partner needs time-limited upload permission to a particular blob without sharing the storage account key.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. That statement describes Storage service endpoints, while the question asks how Blob user-delegation SAS works: A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
Blob Inventory produces scheduled object inventories without crawling each object individually. It belongs to Blob inventory. The stated architecture instead relies on: A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
A retrying order processor may receive the same message multiple times and must avoid duplicate billing. The acceptance test is: Two deliveries of the same order ID create only one invoice. Which design recommendation best satisfies both?
At-least-once message delivery requires application logic to deduplicate business side effects. The selected architecture is design an idempotent handler using a durable business operation key; confirm the result by checking that two deliveries of the same order ID create only one invoice.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. The relevant requirement is: A retrying order processor may receive the same message multiple times and must avoid duplicate billing.
Edge caching reduces origin load and latency for eligible cacheable content. That is useful for Azure Front Door caching (A global website serves the same static assets to users on several continents). It does not meet the current Reliable exactly-once effect requirement: A retrying order processor may receive the same message multiple times and must avoid duplicate billing.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. It does not solve the specified Reliable exactly-once effect condition.
A solution must address both ADF tumbling window and Data Factory hybrid copy. First requirement: A nightly ingestion job must process every hourly window and backfill missed intervals after outages. Second requirement: A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port. Select TWO recommendations that meet these independent needs.
For the ADF tumbling window half of this two-part design, tumbling-window triggers model contiguous time slices with support for backfill. Verify: A missed hour is scheduled for a controlled rerun rather than silently skipped. The other half concerns Data Factory hybrid copy.
For the Data Factory hybrid copy half of this design, self-hosted integration runtime initiates supported outbound communications to access private sources. Check: The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions. The other half concerns ADF tumbling window.
Mapping data flows transform data on managed Spark compute from graphical mappings. The corresponding task is ADF mapping data flow: An analyst wants a GUI-defined transformation over millions of input rows without maintaining Spark scripts. It is not one of the two requested controls (ADF tumbling window and Data Factory hybrid copy).
Partner event integration routes supported third-party event types without custom polling. That plan is appropriate for Event Grid partner events. The two controls sought here are ADF tumbling window and Data Factory hybrid copy.
Pipeline control flow can orchestrate dependent stages instead of independent schedules. Its own validation would be: A simulated first-step failure prevents the downstream write and raises the failure path. The current paired requirement is ADF tumbling window and Data Factory hybrid copy.
A rollout addressing Data Factory hybrid copy has reached acceptance testing. The original problem was: A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port. Which finding verifies its resolution?
Self-hosted integration runtime initiates supported outbound communications to access private sources. Confirm using the measurable result: The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. The distinguishing check is: The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. The Private integration access test checks the pipeline reads the database through the authorized private path while public access fails; the relevant outcome is The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
Partner event integration routes supported third-party event types without custom polling. The offered observation would demonstrate Event Grid partner events: A partner-created event triggers only matching subscriptions across the consuming applications. The current validation is different: The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
An architect must sign off on Synthetic uptime. The business problem is: A public site sometimes fails before user telemetry is received and operations need outside-in availability tests. What observed test result provides valid evidence?
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. Confirm using the measurable result: A deliberate endpoint outage is detected from multiple test locations before users file reports.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The offered observation would demonstrate Log anomaly alert: A controlled failed-login burst creates the specified log-query alert with source IP context. The current validation is different: A deliberate endpoint outage is detected from multiple test locations before users file reports.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. Those observations validate Private observability. They do not establish the required Synthetic uptime result: A deliberate endpoint outage is detected from multiple test locations before users file reports.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. The distinguishing check is: A deliberate endpoint outage is detected from multiple test locations before users file reports.
The Chaos failure testing review proposes: Run controlled fault-injection or chaos tests with clear guardrails and rollback. Which Azure behavior is the technical justification for this decision?
Fault injection tests whether resilience patterns work under realistic failure conditions. It is material here because a distributed app passes unit tests but its failover behavior under partial dependency loss is unknown.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Fault injection tests whether resilience patterns work under realistic failure conditions.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. It belongs to Cosmos multi-write availability. The stated architecture instead relies on: Fault injection tests whether resilience patterns work under realistic failure conditions.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. That statement describes Application Gateway zone redundancy, while the question asks how Chaos failure testing works: Fault injection tests whether resilience patterns work under realistic failure conditions.
Architecture review: RBAC custom role and Role assignment scope. Requirement A: A service team needs a narrow set of resource restart and read operations absent from built-in roles. Requirement B: An engineer only operates one network resource group but has Contributor for the whole subscription. Which complete two-part proposal satisfies both constraints?
For requirement A, custom role actions can grant specific management operations without broad Contributor rights. For requirement B, RBAC assignments inherit downward so narrower scope reduces unintended changes. Verify both independently: The operator restarts an approved service and cannot modify resource access assignments; The engineer can change the assigned network group but not another group's resources.
The option covers one requirement but substitutes Defender compliance for Role assignment scope. The missing acceptance result is: The engineer can change the assigned network group but not another group's resources.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The other proposed action (configure Cost Management budgets and alert thresholds) does not implement the first control. Custom role actions can grant specific management operations without broad Contributor rights.
This combines Cost budgets and Defender compliance, which do not satisfy the distinct requirements for RBAC custom role and Role assignment scope.
The team has justified its Landing zones design with: Adopt an Azure landing-zone architecture following the Cloud Adoption Framework. Which statement accurately describes why the approach works?
Landing zones combine platform foundations with repeatable application subscription governance. It is material here because a growing organization needs repeatable subscriptions with identity, network and governance baselines.
RBAC assignments inherit downward so narrower scope reduces unintended changes. That statement describes Role assignment scope, while the question asks how Landing zones works: Landing zones combine platform foundations with repeatable application subscription governance.
Cost exports provide detailed recurring usage data for downstream allocation reporting. Landing zones combine platform foundations with repeatable application subscription governance.
Azure service quotas are often scoped by subscription and region and can constrain deployability. Landing zones combine platform foundations with repeatable application subscription governance.
A storage service must have an address in a VNet and reject access from the public internet. Which Azure architecture would most directly achieve the required result: The data source resolves to a VNet private address and public access is denied?
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. The selected architecture is use Azure Private Link private endpoint with private DNS and disable public access; confirm the result by checking that the data source resolves to a VNet private address and public access is denied.
Azure Firewall provides managed stateful filtering with network/application rule models. The relevant requirement is: A storage service must have an address in a VNet and reject access from the public internet.
Private endpoints provide a private inbound path for supported App Service access. It does not solve the specified Private endpoint condition.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. That is useful for Virtual WAN global hubs (A multinational firm needs centrally managed branch and VNet transit across many regions). It does not meet the current Private endpoint requirement: A storage service must have an address in a VNet and reject access from the public internet.
For ADF mapping data flow, operations are closing a change that addressed: An analyst wants a GUI-defined transformation over millions of input rows without maintaining Spark scripts. Which post-change signal belongs in the acceptance record?
Mapping data flows transform data on managed Spark compute from graphical mappings. Confirm using the measurable result: The pipeline produces the expected transformed dataset at planned throughput.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. The offered observation would demonstrate Databricks Delta Lake: A MERGE updates matching records atomically and table history contains the transaction. The current validation is different: The pipeline produces the expected transformed dataset at planned throughput.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Those observations validate Synapse dedicated SQL. They do not establish the required ADF mapping data flow result: The pipeline produces the expected transformed dataset at planned throughput.
Partner event integration routes supported third-party event types without custom polling. The distinguishing check is: The pipeline produces the expected transformed dataset at planned throughput.
The target environment adopts this approach for Physical server migration: Use an Azure Migrate-supported physical-server or agent-based migration approach. What property makes it suitable?
Physical migration requires source capture and replication methods different from VMware agentless VM migration. It is material here because a legacy application runs on a physical Windows server and needs an IaaS move.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. Physical migration requires source capture and replication methods different from VMware agentless VM migration.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. That statement describes Retire unused services, while the question asks how Physical server migration works: Physical migration requires source capture and replication methods different from VMware agentless VM migration.
Rebuild replaces the application rather than merely moving its binaries. Physical migration requires source capture and replication methods different from VMware agentless VM migration.
Please check your mailbox for a message from support@examlabs.com and follow the directions.