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
Before approving Vault network boundary, the reviewer assesses this requirement: A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients. Which of the reported outcomes is decisive?
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. Confirm using the measurable result: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Those observations validate Key Vault secrets. They do not establish the required Vault network boundary result: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Authentication strengths let Conditional Access require supported strong methods based on conditions. The distinguishing check is: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
App-only permissions grant service principal operations without a delegated signed-in user. The Application permissions test checks the service obtains an app-only token and performs only the approved Graph actions; the relevant outcome is A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
An acquired system has a temporary documented exception to an encryption rule with an expiration date. An engineer must deliver the following acceptance evidence: The exception is visible in compliance reports and expires on the documented date. What design choice is defensible?
Policy exemptions record approved exceptions while the policy remains assigned. The selected architecture is create a scoped policy exemption with justification and expiry rather than deleting the baseline assignment; confirm the result by checking that the exception is visible in compliance reports and expires on the documented date.
Policy deny or audit effects can enforce required metadata at supported resource scopes. That is useful for Required tag policy (Cost reporting is missing the billing cost center tag on newly created resources). It does not meet the current Policy exemption requirement: An acquired system has a temporary documented exception to an encryption rule with an expiration date.
Initiatives bundle related policy rules and support shared compliance reporting. It does not solve the specified Policy exemption condition.
Policy evaluates resource deployment properties and rejects noncompliant regions. The current need is: An acquired system has a temporary documented exception to an encryption rule with an expiration date.
Architecture review: Blob immutability and ADLS ACLs. Requirement A: Legal records must be WORM protected against modification for five years. Requirement B: A Spark job has storage RBAC access at container level but must isolate sensitive folders. Which complete two-part proposal satisfies both constraints?
For requirement A, immutable storage prevents overwrite and delete during the configured retention interval. For requirement B, directory ACLs provide path-level data authorization when hierarchical namespace is enabled. Verify both independently: An authorized user cannot modify a protected retained object before expiry; A test identity reads its assigned folder but is denied a sibling folder.
Immutable storage prevents overwrite and delete during the configured retention interval. Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. The proposed steps (enable hierarchical namespace and use Azure Data Lake Storage Gen2 capabilities; enable Blob versioning with retention controls) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Blob HNS namespace for Blob immutability. The missing acceptance result is: An authorized user cannot modify a protected retained object before expiry.
One action is correct. The other targets Blob versioning, leaving ADLS ACLs unsolved. Its necessary action is: Configure suitable POSIX-style data lake ACLs and scope broader RBAC intentionally.
For the Durable Functions orchestration requirement, the proposed architecture uses: Choose Durable Functions with explicit orchestrator and activity functions. Why does that design fit?
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. It is material here because a serverless order process needs retries and persisted orchestration across multiple long-running steps.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. Durable orchestrations checkpoint progress and coordinate stateful serverless workflows.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Durable orchestrations checkpoint progress and coordinate stateful serverless workflows.
Asynchronous projections can lag writes and need clear read-after-write expectations. That statement describes Eventual consistency UX, while the question asks how Durable Functions orchestration works: Durable orchestrations checkpoint progress and coordinate stateful serverless workflows.
A rollout addressing SQL auditing has reached acceptance testing. The original problem was: Compliance requires records of login attempts and selected database actions independent of app logs. Which finding verifies its resolution?
SQL auditing captures database events as configured separately from application request telemetry. Confirm using the measurable result: A controlled login and database action appear in the configured audit destination.
Hyperscale decouples storage scale from compute and supports large database sizes. Those observations validate SQL Hyperscale growth. They do not establish the required SQL auditing result: A controlled login and database action appear in the configured audit destination.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The SQL geo-replication reporting test checks report queries use the designated secondary and replication lag stays within the accepted bound; the relevant outcome is A controlled login and database action appear in the configured audit destination.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The offered observation would demonstrate SQL dynamic data masking: Support queries return masked values while appropriately authorized principals can access underlying values. The current validation is different: A controlled login and database action appear in the configured audit destination.
An architect must sign off on Azure Files SMB. The business problem is: A legacy Windows application needs a shared SMB file path used by multiple virtual machines. What observed test result provides valid evidence?
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. Confirm using the measurable result: The application opens the shared UNC path from authorized machines.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The distinguishing check is: The application opens the shared UNC path from authorized machines.
Bounded staleness constrains replication read lag according to allowed versions/time. The Cosmos bounded staleness test checks a test secondary read remains within the documented staleness bound; the relevant outcome is The application opens the shared UNC path from authorized machines.
Cosmos DB provides a distributed document database with configurable consistency and throughput. The offered observation would demonstrate Cosmos DB NoSQL: The app reads JSON documents across the planned partitions with predictable latency. The current validation is different: The application opens the shared UNC path from authorized machines.
A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. An engineer must deliver the following acceptance evidence: Failed backend probes remove one instance and healthy zonal instances continue serving. What design choice is defensible?
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The selected architecture is use a supported zone-redundant Standard Load Balancer deployment with health probes; confirm the result by checking that failed backend probes remove one instance and healthy zonal instances continue serving.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Its design target is Circuit breaker behavior. The stated requirement instead concerns: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones.
Read regions bring replicas closer to users without inherently adding multi-write semantics. It does not solve the specified Zone-redundant load balancer condition.
Failover-group listeners abstract the primary location during regional failover. That is useful for SQL failover groups HA (The database service must recover a read/write endpoint when the primary Azure region fails). It does not meet the current Zone-redundant load balancer requirement: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones.
A solution must address both Workload identity federation and Passwordless app connection. First requirement: A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret. Second requirement: A database-backed application currently stores a SQL password even though it runs on Azure infrastructure. Select TWO recommendations that meet these independent needs.
For the Workload identity federation half of this two-part design, federated credentials exchange trusted external OIDC assertions for Entra access tokens. Verify: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected. The other half concerns Passwordless app connection.
For the Passwordless app connection half of this design, Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. Check: The workload queries its database with an Entra token and rotation of the former password has no effect. The other half concerns Workload identity federation.
Key Vault keys can perform cryptographic operations while restricting private key exposure. That plan is appropriate for Key Vault cryptographic signing. The two controls sought here are Workload identity federation and Passwordless app connection.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Its own validation would be: The regional admin can reset an assigned user's password but cannot administer an out-of-scope user. The current paired requirement is Workload identity federation and Passwordless app connection.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. This alternative solves Vault network boundary, while the question separately requires Workload identity federation and Passwordless app connection.
A telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code. A deployment must satisfy this operational criterion: An expected count is emitted for each completed five-minute event window. Which plan is appropriate?
Stream Analytics supports SQL-like processing over streaming sources with time windows. The selected architecture is use Azure Stream Analytics with an appropriate time window query; confirm the result by checking that an expected count is emitted for each completed five-minute event window.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. The current need is: A telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. It does not solve the specified Stream Analytics window condition.
Tumbling-window triggers model contiguous time slices with support for backfill. The relevant requirement is: A telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code.
Three data tasks must run in sequence and stop downstream operations after upstream failure. The acceptance test is: A simulated first-step failure prevents the downstream write and raises the failure path. Which design recommendation best satisfies both?
Pipeline control flow can orchestrate dependent stages instead of independent schedules. The selected architecture is chain ADF pipeline activities with success/failure dependencies; confirm the result by checking that a simulated first-step failure prevents the downstream write and raises the failure path.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. That is useful for Databricks Delta Lake (An ETL architecture needs ACID updates and versioned tables over object storage for Spark workloads). It does not meet the current ADF pipeline dependency requirement: Three data tasks must run in sequence and stop downstream operations after upstream failure.
Partner event integration routes supported third-party event types without custom polling. Its design target is Event Grid partner events. The stated requirement instead concerns: Three data tasks must run in sequence and stop downstream operations after upstream failure.
Tumbling-window triggers model contiguous time slices with support for backfill. It does not solve the specified ADF pipeline dependency condition.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.