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
Architecture review: SQL connection pooling and SQL serverless idle cost. Requirement A: A serverless API makes many short SQL connections and exhausts available database sessions. Requirement B: A dev/test SQL database is idle for long periods but bursts during a short daily test window. Which complete two-part proposal satisfies both constraints?
For requirement A, pooling reuses connections and reduces setup overhead relative to per-request creation. For requirement B, serverless compute can scale usage and pause eligible databases to reduce idle cost. Verify both independently: Connection counts stabilize while expected API throughput is maintained; Compute charges drop during idle periods and the test workload resumes within tolerated delay.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Serverless compute can scale usage and pause eligible databases to reduce idle cost. The proposed steps (select Azure SQL Database for the managed individual database; run Azure SQL migration assessment and remediate feature compatibility findings) address other capabilities instead of this required pair.
Pooling reuses connections and reduces setup overhead relative to per-request creation. The other proposed action (run Azure SQL migration assessment and remediate feature compatibility findings) addresses a different operation. Serverless compute can scale usage and pause eligible databases to reduce idle cost.
The option covers one requirement but substitutes Azure SQL Database single database for SQL connection pooling. The missing acceptance result is: Connection counts stabilize while expected API throughput is maintained.
A rollout addressing Deployment drift has reached acceptance testing. The original problem was: A production app's manually changed resource settings diverge from the approved IaC template. Which finding verifies its resolution?
Azure deployment what-if previews resource changes before applying a template. Confirm using the measurable result: The change report identifies manual drift and approved deployment restores the intended state.
Azure Policy can deny targeted resource types without revoking all contributor operations. The offered observation would demonstrate Resource type restriction: A public IP create is denied while a private subnet deployment proceeds. The current validation is different: The change report identifies manual drift and approved deployment restores the intended state.
Initiatives bundle related policy rules and support shared compliance reporting. Those observations validate Policy initiative. They do not establish the required Deployment drift result: The change report identifies manual drift and approved deployment restores the intended state.
Locks prevent specified management operations even for users with broad Azure RBAC roles. The distinguishing check is: The change report identifies manual drift and approved deployment restores the intended state.
A fleet needs consistent hardened VM images recreated every week from an approved source. An engineer must deliver the following acceptance evidence: New VMs deploy from the approved version and report the expected security baseline. What design choice is defensible?
Compute Gallery distributes managed image versions for repeatable VM deployments. The selected architecture is publish governed VM images through Azure Compute Gallery with a versioning strategy; confirm the result by checking that new VMs deploy from the approved version and report the expected security baseline.
VMSS automates management and scaling of similar VMs in the same workload. The current need is: A fleet needs consistent hardened VM images recreated every week from an approved source.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. It does not solve the specified Azure VM image standard condition.
Durable Functions manages stateful workflows over serverless function executions. The relevant requirement is: A fleet needs consistent hardened VM images recreated every week from an approved source.
A Spark job has storage RBAC access at container level but must isolate sensitive folders. Identify the most suitable implementation for an outcome where a test identity reads its assigned folder but is denied a sibling folder.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. The selected architecture is configure suitable POSIX-style data lake ACLs and scope broader RBAC intentionally; confirm the result by checking that a test identity reads its assigned folder but is denied a sibling folder.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. That is useful for Blob user-delegation SAS (A partner needs time-limited upload permission to a particular blob without sharing the storage account key). It does not meet the current ADLS ACLs requirement: A Spark job has storage RBAC access at container level but must isolate sensitive folders.
Cosmos DB provides a distributed document database with configurable consistency and throughput. Its design target is Cosmos DB NoSQL. The stated requirement instead concerns: A Spark job has storage RBAC access at container level but must isolate sensitive folders.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. It does not solve the specified ADLS ACLs condition.
Build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access. Identify the most suitable implementation for an outcome where a pipeline pushes a signed image and production pulls it without shared registry passwords.
ACR stores OCI images and supports Azure identity-based authorization to the registry. The selected architecture is use Azure Container Registry with controlled image push and pull access; confirm the result by checking that a pipeline pushes a signed image and production pulls it without shared registry passwords.
GPU instances provide accelerators not present on standard CPU-only VMs. Its design target is GPU VM. The stated requirement instead concerns: Build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access.
Redundancy prevents a single host maintenance event from removing the only serving instance. The current need is: Build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access.
Durable Functions manages stateful workflows over serverless function executions. It does not solve the specified Container Registry condition.
Architecture review: Vault network boundary and Key Vault cryptographic signing. Requirement A: A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients. Requirement B: An application must sign payloads with a centrally controlled key without exporting its private material. Which complete two-part proposal satisfies both constraints?
For requirement A, private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. For requirement B, Key Vault keys can perform cryptographic operations while restricting private key exposure. Verify both independently: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path; The application receives a valid signature but cannot export the private key material.
The first step implements Shared workload identity instead of Vault network boundary. The necessary change is to use a Key Vault private endpoint and correctly configured private DNS and firewall policy.
Both proposed halves address other use cases: Shared workload identity and App registration API scopes. The requested pair is Vault network boundary and Key Vault cryptographic signing.
One action is correct. The other targets App registration API scopes, leaving Key Vault cryptographic signing unsolved. Its necessary action is: Use Azure Key Vault key operations with a suitable key type and access permissions.
Node pool capacity becomes insufficient for pending pods during daily traffic peaks. An engineer must deliver the following acceptance evidence: Pending pods move to new nodes before the measured capacity deadline. What design choice is defensible?
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The selected architecture is enable AKS cluster autoscaler within approved node pool bounds; confirm the result by checking that pending pods move to new nodes before the measured capacity deadline.
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. The current need is: Node pool capacity becomes insufficient for pending pods during daily traffic peaks.
A zone-separated standby supports automated failover where offered. It does not solve the specified AKS cluster autoscaler condition.
Availability zones isolate infrastructure failure domains within an enabled region. Its design target is Availability zones for VM tier. The stated requirement instead concerns: Node pool capacity becomes insufficient for pending pods during daily traffic peaks.
The target environment adopts this approach for ADF pipeline dependency: Chain ADF pipeline activities with success/failure dependencies. What property makes it suitable?
Pipeline control flow can orchestrate dependent stages instead of independent schedules. It is material here because three data tasks must run in sequence and stop downstream operations after upstream failure.
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. It belongs to Azure Data Explorer telemetry. The stated architecture instead relies on: Pipeline control flow can orchestrate dependent stages instead of independent schedules.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. That statement describes Service Bus ordering, while the question asks how ADF pipeline dependency works: Pipeline control flow can orchestrate dependent stages instead of independent schedules.
Self-hosted integration runtime initiates supported outbound communications to access private sources. Pipeline control flow can orchestrate dependent stages instead of independent schedules.
Architecture review: Synapse dedicated SQL and Synapse serverless SQL. Requirement A: A large enterprise data warehouse requires predictable reserved compute for repeatable analytic SQL workloads. Requirement B: Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster. Which complete two-part proposal satisfies both constraints?
For requirement A, dedicated pools supply reserved MPP compute suited for managed warehouse workloads. For requirement B, serverless SQL queries external lake files with consumption-based query compute. Verify both independently: The fact-table join finishes within measured performance goals under the planned workload; A SELECT reads the Parquet dataset with no dedicated SQL pool running.
Serverless SQL queries external lake files with consumption-based query compute. The other proposed action (use Data Factory tumbling-window triggers with dependency and retry design) does not implement the first control. Dedicated pools supply reserved MPP compute suited for managed warehouse workloads.
The option covers one requirement but substitutes ADF incremental copy for Synapse serverless SQL. The missing acceptance result is: A SELECT reads the Parquet dataset with no dedicated SQL pool running.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Serverless SQL queries external lake files with consumption-based query compute. The proposed steps (use Data Factory tumbling-window triggers with dependency and retry design; implement watermark-based incremental ingestion with persisted checkpoints) address other capabilities instead of this required pair.
The acceptance criterion for Modernization cost assessment comes from this issue: A migration project chooses premium PaaS services without considering steady-state usage and license rights. Which measured outcome is the strongest proof?
Sizing, licensing and consumption assumptions materially affect target economics. Confirm using the measurable result: The approved target design includes measured compute, storage, network and license costs.
DNS cutover requires propagation and dependency planning independent of VM replication. The offered observation would demonstrate Networking cutover DNS: Clients resolve the new endpoint and the rollback procedure returns traffic if needed. The current validation is different: The approved target design includes measured compute, storage, network and license costs.
Target compatibility determines whether code changes or a different managed target are required. The distinguishing check is: The approved target design includes measured compute, storage, network and license costs.
File Sync preserves local namespace access while synchronizing with Azure file shares. The Azure File Sync test checks frequently used files remain locally available and cold files tier to cloud; the relevant outcome is The approved target design includes measured compute, storage, network and license costs.
For Dedicated host, operations are closing a change that addressed: A regulated app requires a physically dedicated server host for VM placement and host-level isolation. Which post-change signal belongs in the acceptance record?
Dedicated Host provides physical host isolation with separate placement and pricing controls. Confirm using the measurable result: The deployed VMs are listed on the reserved dedicated host.
Confidential VMs use hardware-backed protection for sensitive guest execution environments. Those observations validate Confidential VM. They do not establish the required Dedicated host result: The deployed VMs are listed on the reserved dedicated host.
ASE provides dedicated App Service hosting in a customer virtual-network environment. The distinguishing check is: The deployed VMs are listed on the reserved dedicated host.
General-purpose VMs balance CPU and memory while retaining OS-level control. The General purpose VM test checks the workload runs its required driver within the provisioned compute budget; the relevant outcome is The deployed VMs are listed on the reserved dedicated host.
Please check your mailbox for a message from support@examlabs.com and follow the directions.