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: AKS cluster autoscaler and AKS availability zones. Requirement A: Node pool capacity becomes insufficient for pending pods during daily traffic peaks. Requirement B: A production AKS cluster requires pods and nodes across three availability zones. Which complete two-part proposal satisfies both constraints?
For requirement A, cluster autoscaler adjusts nodes to schedule eligible pending pods. For requirement B, zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. Verify both independently: Pending pods move to new nodes before the measured capacity deadline; After a simulated zone failure, surviving pods maintain API availability and replacement replicas become Ready within the tested recovery window on healthy-zone nodes.
Both proposed halves address other use cases: Azure SQL zone redundancy and VM scale set autoscaling. The requested pair is AKS cluster autoscaler and AKS availability zones.
One action is correct. The other targets VM scale set autoscaling, leaving AKS availability zones unsolved. Its necessary action is: Use zone-aware node pools and workload spread/anti-affinity policies.
The first step implements Azure SQL zone redundancy instead of AKS cluster autoscaler. The necessary change is to enable AKS cluster autoscaler within approved node pool bounds.
Security standards require a reusable collection of tagging, encryption and diagnostics policies. Which Azure architecture would most directly achieve the required result: Compliance reporting shows the member controls under the assigned initiative?
Initiatives bundle related policy rules and support shared compliance reporting. The selected architecture is group relevant definitions into a policy initiative assigned to the correct management scope; confirm the result by checking that compliance reporting shows the member controls under the assigned initiative.
Infrastructure as code declares desired resources and allows review and repeat deployment. That is useful for Standardized IaC (Operations wants reproducible Azure environment deployments from version-controlled definitions). It does not meet the current Policy initiative requirement: Security standards require a reusable collection of tagging, encryption and diagnostics policies.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. It does not solve the specified Policy initiative condition.
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. The relevant requirement is: Security standards require a reusable collection of tagging, encryption and diagnostics policies.
For VM agentless migration, operations are closing a change that addressed: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Which post-change signal belongs in the acceptance record?
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. Confirm using the measurable result: A test migration boots the replicated VM and validates application dependencies.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The offered observation would demonstrate SQL online migration: Source and target reconcile and final cutover falls within the tolerated outage. The current validation is different: A test migration boots the replicated VM and validates application dependencies.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. Those observations validate Rehost versus refactor. They do not establish the required VM agentless migration result: A test migration boots the replicated VM and validates application dependencies.
Replatforming changes hosting characteristics while preserving most app behavior. The distinguishing check is: A test migration boots the replicated VM and validates application dependencies.
Architecture rationale review—Cosmos session consistency: Use Cosmos DB session consistency with proper session token handling. Which explanation accurately distinguishes this capability?
Session consistency offers read-your-writes within a session without strong global consistency. It is material here because a customer portal must read its own updates while accepting that other users may briefly see stale writes.
Soft delete retains recoverable deleted objects or containers during the configured period. Session consistency offers read-your-writes within a session without strong global consistency.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. Session consistency offers read-your-writes within a session without strong global consistency.
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. It belongs to Azure Files SMB. The stated architecture instead relies on: Session consistency offers read-your-writes within a session without strong global consistency.
For the Blob archive rehydration requirement, the proposed architecture uses: Use Blob Archive tier for eligible block blobs with documented rehydration delay. Why does that design fit?
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. It is material here because a seven-year archive is rarely read and recovery can wait hours.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. It belongs to Azure managed disks. The stated architecture instead relies on: Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. That statement describes Cosmos conflict handling, while the question asks how Blob archive rehydration works: Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading.
Architecture review: VM resource health and Cross-tenant operations. Requirement A: A single VM becomes unavailable but the Azure region itself is healthy. Requirement B: An MSP needs delegated visibility into customer Azure resource monitoring without separate customer logins. Which complete two-part proposal satisfies both constraints?
For requirement A, resource Health reports the platform-side availability history of individual Azure resources. For requirement B, lighthouse enables delegated management across tenants without relocating customer-owned resources. Verify both independently: The specific VM shows an unavailable health state while the regional Service Health feed remains normal; Authorized MSP operators view the delegated customer's resource health from their managing tenant.
One action is correct. The other targets Security-event streaming, leaving Cross-tenant operations unsolved. Its necessary action is: Use Azure Lighthouse delegated resource management with least-privilege role assignments.
Resource Health reports the platform-side availability history of individual Azure resources. Lighthouse enables delegated management across tenants without relocating customer-owned resources. The proposed steps (use Azure Policy deployIfNotExists with remediation identity for supported diagnostic settings; route supported platform diagnostic events to an Event Hubs namespace) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Automated diagnostics policy for VM resource health. The missing acceptance result is: The specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Architecture review: Application permissions and App registration API scopes. Requirement A: A scheduled daemon must call Microsoft Graph without an interactive user session. Requirement B: A backend API should expose delegated scopes to a client on behalf of a signed-in user. Which complete two-part proposal satisfies both constraints?
For requirement A, app-only permissions grant service principal operations without a delegated signed-in user. For requirement B, delegated permissions represent what an application can do on behalf of an authenticated user. Verify both independently: The service obtains an app-only token and performs only the approved Graph actions; The API token contains the required scope and access without that scope is rejected.
App-only permissions grant service principal operations without a delegated signed-in user. The other proposed action (grant a suitable storage data role at the narrow supported resource scope) addresses a different operation. Delegated permissions represent what an application can do on behalf of an authenticated user.
The option covers one requirement but substitutes Vault network boundary for Application permissions. The missing acceptance result is: The service obtains an app-only token and performs only the approved Graph actions.
App-only permissions grant service principal operations without a delegated signed-in user. Delegated permissions represent what an application can do on behalf of an authenticated user. The proposed steps (use a Key Vault private endpoint and correctly configured private DNS and firewall policy; grant a suitable storage data role at the narrow supported resource scope) address other capabilities instead of this required pair.
A service private endpoint resolves to a public address from a peered spoke VNet. The acceptance test is: A lookup from the spoke resolves the service FQDN to the intended private IP. Which design recommendation best satisfies both?
Private DNS zone links determine name resolution for VNets that consume private endpoints. The selected architecture is link the appropriate Azure Private DNS zone and configure private endpoint DNS records; confirm the result by checking that a lookup from the spoke resolves the service FQDN to the intended private IP.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The current need is: A service private endpoint resolves to a public address from a peered spoke VNet.
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. It does not solve the specified DNS private zones condition.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. Its design target is DDoS protection. The stated requirement instead concerns: A service private endpoint resolves to a public address from a peered spoke VNet.
A team member needs read-only access to selected vault secrets but should not grant access policies. An architecture board will approve a solution only if this outcome is demonstrated: The user retrieves authorized secret values but cannot alter vault access configuration. What should be selected?
Key Vault RBAC data permissions differ from vault resource-management permissions. The selected architecture is assign a suitable Key Vault data-plane RBAC role at a supported minimal scope; confirm the result by checking that the user retrieves authorized secret values but cannot alter vault access configuration.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The current need is: A team member needs read-only access to selected vault secrets but should not grant access policies.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. Its design target is Vault network boundary. The stated requirement instead concerns: A team member needs read-only access to selected vault secrets but should not grant access policies.
Access reviews periodically recertify assigned access and can remove access for denied reviews. It does not solve the specified Vault RBAC least privilege condition.
Architecture review: Azure HPC design and Dedicated host. Requirement A: A parallel scientific workload depends on low-latency internode communication and high-performance storage. Requirement B: A regulated app requires a physically dedicated server host for VM placement and host-level isolation. Which complete two-part proposal satisfies both constraints?
For requirement A, HPC workloads require specialized low-latency fabric support beyond commodity VMs. For requirement B, dedicated Host provides physical host isolation with separate placement and pricing controls. Verify both independently: MPI benchmark meets its target communication latency across allocated nodes; The deployed VMs are listed on the reserved dedicated host.
One action is correct. The other targets App Service isolation, leaving Dedicated host unsolved. Its necessary action is: Evaluate Azure Dedicated Host with the needed VM families and capacity.
This combines Container Registry and App Service isolation, which do not satisfy the distinct requirements for Azure HPC design and Dedicated host.
The option covers one requirement but substitutes Container Registry for Azure HPC design. The missing acceptance result is: MPI benchmark meets its target communication latency across allocated nodes.
The target environment adopts this approach for Blob vaulted backup: Evaluate supported vaulted backup for blobs with documented feature and region limits. What property makes it suitable?
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. It is material here because compliance requires offsite protected copies of blob data separate from only operational object versioning.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. That statement describes Backup private endpoints, while the question asks how Blob vaulted backup works: Vaulted blob backup supplies protected backup storage with different capabilities than operational backups.
RTO is the maximum acceptable restoration duration, not the amount of lost data. Vaulted blob backup supplies protected backup storage with different capabilities than operational backups.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. It belongs to Blob operational backup. The stated architecture instead relies on: Vaulted blob backup supplies protected backup storage with different capabilities than operational backups.
Please check your mailbox for a message from support@examlabs.com and follow the directions.