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
A small branch needs encrypted connectivity to a VNet over its existing internet link. Identify the most suitable implementation for an outcome where encrypted traffic reaches the approved private Azure subnet from the branch.
VPN Gateway can establish encrypted IPsec tunnels over public networks. The selected architecture is deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings; confirm the result by checking that encrypted traffic reaches the approved private Azure subnet from the branch.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. It does not solve the specified Site-to-site VPN condition.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. The current need is: A small branch needs encrypted connectivity to a VNet over its existing internet link.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. That is useful for VNet peering (Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways). It does not meet the current Site-to-site VPN requirement: A small branch needs encrypted connectivity to a VNet over its existing internet link.
A solution must address both Azure Functions event and Autoscaling based on queue. First requirement: A short-running event handler reacts to storage events and must scale without provisioned servers. Second requirement: A processing worker should scale according to Service Bus backlog, not HTTP request count. Select TWO recommendations that meet these independent needs.
For the Autoscaling based on queue half of this design, queue-length scaling aligns worker count with pending work rather than idle CPU metrics. Check: The number of workers grows with queue backlog and contracts after processing. The other half concerns Azure Functions event.
For the Azure Functions event half of this two-part design, functions supplies event-driven serverless execution with plan-specific scale and timeout limits. Verify: A matching event triggers the function within the required processing window. The other half concerns Autoscaling based on queue.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. This alternative solves Azure HPC design, while the question separately requires Azure Functions event and Autoscaling based on queue.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. That plan is appropriate for Memory optimized VM. The two controls sought here are Azure Functions event and Autoscaling based on queue.
Container Apps provides managed container hosting and microservice scale with KEDA capabilities. Its own validation would be: A new revision handles traffic and scales down when request demand is low. The current paired requirement is Azure Functions event and Autoscaling based on queue.
For the Private inbound App Service requirement, the proposed architecture uses: Use an App Service private endpoint with private DNS and access restrictions. Why does that design fit?
Private endpoints provide a private inbound path for supported App Service access. It is material here because an App Service must accept requests only through the corporate private network.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. Private endpoints provide a private inbound path for supported App Service access.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. That statement describes Private endpoint, while the question asks how Private inbound App Service works: Private endpoints provide a private inbound path for supported App Service access.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Private endpoints provide a private inbound path for supported App Service access.
Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault. Identify the most suitable implementation for an outcome where the database reports the approved key as its TDE protector and follows documented key rotation.
CMK encryption protects database data at rest while keys are managed under customer control. The selected architecture is configure customer-managed transparent data encryption protector where supported; confirm the result by checking that the database reports the approved key as its TDE protector and follows documented key rotation.
Business Critical uses a local SSD-oriented architecture with high availability replicas. That is useful for Business Critical SQL latency (A transaction-heavy database requires low latency local SSD and multiple synchronous replicas within the region). It does not meet the current SQL customer-managed keys requirement: Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. The relevant requirement is: Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. It does not solve the specified SQL customer-managed keys condition.
For the Dedicated host requirement, the proposed architecture uses: Evaluate Azure Dedicated Host with the needed VM families and capacity. Why does that design fit?
Dedicated Host provides physical host isolation with separate placement and pricing controls. It is material here because a regulated app requires a physically dedicated server host for VM placement and host-level isolation.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That statement describes App Service isolation, while the question asks how Dedicated host works: Dedicated Host provides physical host isolation with separate placement and pricing controls.
Confidential VMs use hardware-backed protection for sensitive guest execution environments. Dedicated Host provides physical host isolation with separate placement and pricing controls.
General-purpose VMs balance CPU and memory while retaining OS-level control. Dedicated Host provides physical host isolation with separate placement and pricing controls.
A rollout addressing Spot VM suitability has reached acceptance testing. The original problem was: A rendering workload can checkpoint and tolerate eviction but has a tight compute budget. Which finding verifies its resolution?
Spot instances offer lower-priced spare capacity without guaranteed availability. Confirm using the measurable result: An eviction event restarts work from its last saved checkpoint on available capacity.
ASE provides dedicated App Service hosting in a customer virtual-network environment. The offered observation would demonstrate App Service isolation: The app operates in the required isolated hosting boundary and passes private connectivity tests. The current validation is different: An eviction event restarts work from its last saved checkpoint on available capacity.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. Those observations validate Azure HPC design. They do not establish the required Spot VM suitability result: An eviction event restarts work from its last saved checkpoint on available capacity.
GPU instances provide accelerators not present on standard CPU-only VMs. The GPU VM test checks the model uses available GPU memory and meets measured inference latency; the relevant outcome is An eviction event restarts work from its last saved checkpoint on available capacity.
The design team completed work on Databricks Delta Lake. Its governing requirement was: An ETL architecture needs ACID updates and versioned tables over object storage for Spark workloads. Identify the conclusive verification result.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. Confirm using the measurable result: A MERGE updates matching records atomically and table history contains the transaction.
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 Databricks Delta Lake result: A MERGE updates matching records atomically and table history contains the transaction.
Partner event integration routes supported third-party event types without custom polling. The distinguishing check is: A MERGE updates matching records atomically and table history contains the transaction.
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: A MERGE updates matching records atomically and table history contains the transaction.
To validate the Disk snapshot consistency deployment, reviewers revisit this operational need: A multi-disk database VM needs a rollback that does not corrupt an in-flight transaction. What result confirms it was met?
Independent crash-consistent snapshots may not preserve database write ordering across disks. Confirm using the measurable result: Restored database passes integrity checks and represents a consistent recovery point.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. The distinguishing check is: Restored database passes integrity checks and represents a consistent recovery point.
Compute replication does not automatically guarantee complete application network reachability. The Azure-to-Azure ASR networking test checks a test failover can reach the recovered app through the intended private routes; the relevant outcome is Restored database passes integrity checks and represents a consistent recovery point.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The offered observation would demonstrate SQL geo-restore: A region-loss exercise recovers a database from the latest supported geo backup. The current validation is different: Restored database passes integrity checks and represents a consistent recovery point.
A multi-disk database VM needs a rollback that does not corrupt an in-flight transaction. The acceptance test is: Restored database passes integrity checks and represents a consistent recovery point. Which design recommendation best satisfies both?
Independent crash-consistent snapshots may not preserve database write ordering across disks. The selected architecture is use application-consistent backup or coordinated snapshot mechanisms rather than uncoordinated disk copies; confirm the result by checking that restored database passes integrity checks and represents a consistent recovery point.
Multi-user authorization separates approval boundaries for critical backup changes. Its design target is Multifactor critical operations. The stated requirement instead concerns: A multi-disk database VM needs a rollback that does not corrupt an in-flight transaction.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. The relevant requirement is: A multi-disk database VM needs a rollback that does not corrupt an in-flight transaction.
Share snapshots preserve file-share point-in-time state for supported restoration. It does not solve the specified Disk snapshot consistency condition.
A proposed solution for App Service web is: Choose Azure App Service on a suitable tier with deployment slots. Select the strongest statement supporting the recommendation.
App Service manages web hosting and supports deployment slots on eligible plans. It is material here because an HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team.
Encryption sets connect managed disk encryption to customer-owned keys. App Service manages web hosting and supports deployment slots on eligible plans.
GPU instances provide accelerators not present on standard CPU-only VMs. It belongs to GPU VM. The stated architecture instead relies on: App Service manages web hosting and supports deployment slots on eligible plans.
VMSS automates management and scaling of similar VMs in the same workload. That statement describes VMSS dynamic scaling, while the question asks how App Service web works: App Service manages web hosting and supports deployment slots on eligible plans.
The design team completed work on APIM rate limiting. Its governing requirement was: A popular API needs to reject excessive client requests without changing back-end services. Identify the conclusive verification result.
APIM can enforce per-client API consumption controls before requests reach backends. Confirm using the measurable result: A burst beyond the quota is throttled while permitted traffic proceeds.
At-least-once message delivery requires application logic to deduplicate business side effects. Those observations validate Reliable exactly-once effect. They do not establish the required APIM rate limiting result: A burst beyond the quota is throttled while permitted traffic proceeds.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The distinguishing check is: A burst beyond the quota is throttled while permitted traffic proceeds.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. The Application Gateway path routing test checks requests to each path arrive at the correct healthy backend pool; the relevant outcome is A burst beyond the quota is throttled while permitted traffic proceeds.
Please check your mailbox for a message from support@examlabs.com and follow the directions.