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
The design team completed work on Role assignment scope. Its governing requirement was: An engineer only operates one network resource group but has Contributor for the whole subscription. Identify the conclusive verification result.
RBAC assignments inherit downward so narrower scope reduces unintended changes. Confirm using the measurable result: The engineer can change the assigned network group but not another group's resources.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Those observations validate Subscription isolation. They do not establish the required Role assignment scope result: The engineer can change the assigned network group but not another group's resources.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The Defender compliance test checks a noncompliant resource is reported under the relevant regulatory control; the relevant outcome is The engineer can change the assigned network group but not another group's resources.
DeployIfNotExists requires remediation for already deployed resources where appropriate. The offered observation would demonstrate Policy remediation: The noncompliant existing resources receive the required settings without manual per-resource editing. The current validation is different: The engineer can change the assigned network group but not another group's resources.
Short-lived environments must be removed together without deleting shared platform services. An architecture board will approve a solution only if this outcome is demonstrated: Deleting an approved test resource group removes only the intended environment resources. What should be selected?
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. The selected architecture is group environment-owned resources into lifecycle-aligned resource groups; confirm the result by checking that deleting an approved test resource group removes only the intended environment resources.
Policy exemptions record approved exceptions while the policy remains assigned. That is useful for Policy exemption (An acquired system has a temporary documented exception to an encryption rule with an expiration date). It does not meet the current Resource group lifecycle requirement: Short-lived environments must be removed together without deleting shared platform services.
Budgets monitor and notify about spending and do not automatically stop resources. It does not solve the specified Resource group lifecycle condition.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The relevant requirement is: Short-lived environments must be removed together without deleting shared platform services.
A solution must address both Secrets in deployment pipeline and Key Vault secrets. First requirement: An IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control. Second requirement: A service depends on a vendor API password that rotates frequently. Select TWO recommendations that meet these independent needs.
For the Key Vault secrets half of this design, Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Check: The service uses the new secret version without an embedded password in deployment artifacts. The other half concerns Secrets in deployment pipeline.
For the Secrets in deployment pipeline half of this two-part design, secure secret handling removes reusable credentials from source while preserving automation. Verify: The committed deployment files contain no functional credentials and the deployment still succeeds. The other half concerns Key Vault secrets.
Data-plane roles control access to blob content and least-scope assignment reduces unnecessary privileges. This alternative solves Managed-identity scope, while the question separately requires Secrets in deployment pipeline and Key Vault secrets.
App-only permissions grant service principal operations without a delegated signed-in user. That plan is appropriate for Application permissions. The two controls sought here are Secrets in deployment pipeline and Key Vault secrets.
A user-assigned identity has a lifecycle separate from each consuming Azure resource. Its own validation would be: Both functions access the approved store and identity remains after one app is replaced. The current paired requirement is Secrets in deployment pipeline and Key Vault secrets.
For Durable Functions orchestration, operations are closing a change that addressed: A serverless order process needs retries and persisted orchestration across multiple long-running steps. Which post-change signal belongs in the acceptance record?
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. Confirm using the measurable result: Restarting a worker does not restart already completed business steps.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. The offered observation would demonstrate Application Gateway path routing: Requests to each path arrive at the correct healthy backend pool. The current validation is different: Restarting a worker does not restart already completed business steps.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Those observations validate API Management gateway. They do not establish the required Durable Functions orchestration result: Restarting a worker does not restart already completed business steps.
Asynchronous projections can lag writes and need clear read-after-write expectations. The distinguishing check is: Restarting a worker does not restart already completed business steps.
A solution must address both Front Door global failover and Zone-redundant load balancer. First requirement: Two regional web endpoints need internet-edge routing and automatic failover to a healthy region. Second requirement: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. Select TWO recommendations that meet these independent needs.
For the Front Door global failover half of this two-part design, Front Door provides global application delivery and HTTP(S) origin failover at the edge. Verify: Requests shift to healthy origin after simulated regional endpoint failure. The other half concerns Zone-redundant load balancer.
For the Zone-redundant load balancer half of this design, load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Check: Failed backend probes remove one instance and healthy zonal instances continue serving. The other half concerns Front Door global failover.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The corresponding task is Cosmos multi-write availability: A global application must continue accepting writes from multiple regions when one region fails. It is not one of the two requested controls (Front Door global failover and Zone-redundant load balancer).
Zone-distributed nodes and pod scheduling reduce concentration, but a zone loss can leave pods Pending unless healthy-zone node capacity, quota, volume topology and scheduling constraints permit recovery. That plan is appropriate for AKS availability zones. The two controls sought here are Front Door global failover and Zone-redundant load balancer.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The corresponding task is AKS cluster autoscaler: Node pool capacity becomes insufficient for pending pods during daily traffic peaks. It is not one of the two requested controls (Front Door global failover and Zone-redundant load balancer).
A solution must address both Control-plane audit and Cross-subscription workspace. First requirement: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Second requirement: Four subscriptions must be searched together during incident response with one KQL query and shared retention policy. Select TWO recommendations that meet these independent needs.
For the Control-plane audit half of this two-part design, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify: A denied deployment and a successful resource deletion appear with caller and operation name. The other half concerns Cross-subscription workspace.
For the Cross-subscription workspace half of this design, a workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. Check: The same query returns events labeled with all four source subscription IDs. The other half concerns Control-plane audit.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. That plan is appropriate for Security-event streaming. The two controls sought here are Control-plane audit and Cross-subscription workspace.
Resource Health reports the platform-side availability history of individual Azure resources. Its own validation would be: The specific VM shows an unavailable health state while the regional Service Health feed remains normal. The current paired requirement is Control-plane audit and Cross-subscription workspace.
KQL summarizes timestamped structured log data across dimensions such as operation and cloud role. The corresponding task is Error trend queries: Operations must aggregate intermittent HTTP 500s by service and hour from application traces. It is not one of the two requested controls (Control-plane audit and Cross-subscription workspace).
The target environment adopts this approach for SQL ledger immutability: Evaluate Azure SQL ledger tables with verifiable database digests. What property makes it suitable?
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. It is material here because auditors require cryptographic evidence that transaction history was not tampered with after posting.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Ledger records cryptographically verifiable tamper-evidence for supported relational tables.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Ledger records cryptographically verifiable tamper-evidence for supported relational tables.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. It belongs to SQL schema isolation. The stated architecture instead relies on: Ledger records cryptographically verifiable tamper-evidence for supported relational tables.
Before approving Security-event streaming, the reviewer assesses this requirement: The SOC streams resource events into an external SIEM and needs independent replay and consumer handling. Which of the reported outcomes is decisive?
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. Confirm using the measurable result: A test operation appears in the Event Hub stream and can be read by the SIEM consumer.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. The offered observation would demonstrate Automated diagnostics policy: A newly provisioned supported storage account gets the intended diagnostics after policy remediation. The current validation is different: A test operation appears in the Event Hub stream and can be read by the SIEM consumer.
Action groups define notifications and automated responses and can be reused by alert rules. The distinguishing check is: A test operation appears in the Event Hub stream and can be read by the SIEM consumer.
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. The Synthetic uptime test checks a deliberate endpoint outage is detected from multiple test locations before users file reports; the relevant outcome is A test operation appears in the Event Hub stream and can be read by the SIEM consumer.
Architecture review: VM agentless migration and SQL offline migration. Requirement A: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Requirement B: A small SQL database can tolerate a planned maintenance outage for cutover. Which complete two-part proposal satisfies both constraints?
For requirement A, server migration replication supports lift-and-shift of eligible VM workloads to Azure. For requirement B, offline migration can simplify cutover when application downtime is acceptable. Verify both independently: A test migration boots the replicated VM and validates application dependencies; The migrated database passes consistency checks before reopening writes.
Both proposed halves address other use cases: Networking cutover DNS and Modernization cost assessment. The requested pair is VM agentless migration and SQL offline migration.
One action is correct. The other targets Networking cutover DNS, leaving VM agentless migration unsolved. Its necessary action is: Use an appropriate Azure Migrate server migration path after appliance assessment.
The mismatched half is Modernization cost assessment; SQL offline migration instead needs: Use an appropriate offline Azure Database Migration Service path after compatibility review.
Architecture review: Resource lock constraints and Resource RBAC versus data access. Requirement A: An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes. Requirement B: A user can view a storage account resource but cannot download its blobs. Which complete two-part proposal satisfies both constraints?
For requirement A, management locks guard against accidental resource deletes and operate separately from authorization roles. For requirement B, management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. Verify both independently: Authorized configuration updates succeed but the delete operation is blocked; The user downloads an approved blob without gaining storage management privileges.
One action is correct. The other targets Azure Files identity access, leaving Resource lock constraints unsolved. Its necessary action is: Add an appropriate CanNotDelete lock while maintaining suitable RBAC permissions.
This combines Azure Files identity access and Key Vault secrets, which do not satisfy the distinct requirements for Resource lock constraints and Resource RBAC versus data access.
The option covers one requirement but substitutes Key Vault secrets for Resource RBAC versus data access. The missing acceptance result is: The user downloads an approved blob without gaining storage management privileges.
Before approving Agent collection rules, the reviewer assesses this requirement: Windows servers send performance counters that should differ by workload and environment. Which of the reported outcomes is decisive?
DCRs specify collected streams destinations and transformations for supported agent sources. Confirm using the measurable result: Production servers send approved counters while test servers omit the excluded stream.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The Immutable evidence archive test checks a retained log blob rejects unauthorized deletion during its compliance retention window; the relevant outcome is Production servers send approved counters while test servers omit the excluded stream.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Those observations validate Azure service health. They do not establish the required Agent collection rules result: Production servers send approved counters while test servers omit the excluded stream.
Analytics and longer-term retention options have different query and storage cost characteristics. The distinguishing check is: Production servers send approved counters while test servers omit the excluded stream.
Please check your mailbox for a message from support@examlabs.com and follow the directions.