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 solution must address both Hybrid route validation and VM agentless migration. First requirement: Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute. Second requirement: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Select TWO recommendations that meet these independent needs.
For the Hybrid route validation half of this two-part design, hybrid reachability depends on both routing and security decisions in the destination VNet. Verify: The Azure workload connects to on-prem data through the approved private network path. The other half concerns VM agentless migration.
For the VM agentless migration half of this design, server migration replication supports lift-and-shift of eligible VM workloads to Azure. Check: A test migration boots the replicated VM and validates application dependencies. The other half concerns Hybrid route validation.
Rebuild replaces the application rather than merely moving its binaries. That plan is appropriate for Rebuild cloud native. The two controls sought here are Hybrid route validation and VM agentless migration.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. This alternative solves Migration landing zone, while the question separately requires Hybrid route validation and VM agentless migration.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The corresponding task is SQL online migration: A high-volume database allows little cutover downtime and must synchronize changes before switch. It is not one of the two requested controls (Hybrid route validation and VM agentless migration).
The team has justified its Azure HPC design design with: Design HPC compute with suitable InfiniBand/RDMA VM families and network placement. Which statement accurately describes why the approach works?
HPC workloads require specialized low-latency fabric support beyond commodity VMs. It is material here because a parallel scientific workload depends on low-latency internode communication and high-performance storage.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That statement describes App Service isolation, while the question asks how Azure HPC design works: HPC workloads require specialized low-latency fabric support beyond commodity VMs.
VMSS automates management and scaling of similar VMs in the same workload. HPC workloads require specialized low-latency fabric support beyond commodity VMs.
App Service manages web hosting and supports deployment slots on eligible plans. HPC workloads require specialized low-latency fabric support beyond commodity VMs.
Customer support may query a user table but should not see complete personal identifiers in routine result sets. A deployment must satisfy this operational criterion: Support queries return masked values while appropriately authorized principals can access underlying values. Which plan is appropriate?
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The selected architecture is configure SQL dynamic data masking for selected columns and test permission bypass behavior; confirm the result by checking that support queries return masked values while appropriately authorized principals can access underlying values.
Business Critical uses a local SSD-oriented architecture with high availability replicas. It does not solve the specified SQL dynamic data masking condition.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The relevant requirement is: Customer support may query a user table but should not see complete personal identifiers in routine result sets.
Azure SQL Database offers fully managed relational database operations with automated backups. The current need is: Customer support may query a user table but should not see complete personal identifiers in routine result sets.
A solution must address both PIM on-demand roles and Conditional MFA. First requirement: Cloud operations needs eligible administrators to activate subscription Owner only during approved maintenance. Second requirement: Administrators must use phishing-resistant authentication for high-privilege cloud portal actions. Select TWO recommendations that meet these independent needs.
For the Conditional MFA half of this design, authentication strengths let Conditional Access require supported strong methods based on conditions. Check: The admin can sign in with a compliant method and a weaker method is rejected. The other half concerns PIM on-demand roles.
For the PIM on-demand roles half of this two-part design, PIM can time-bound eligible role activation with approvals MFA and justification. Verify: An eligible operator activates access for the window and loses elevation after expiry. The other half concerns Conditional MFA.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. This alternative solves Managed identity for App Service, while the question separately requires PIM on-demand roles and Conditional MFA.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. The corresponding task is Key Vault certificate lifecycle: A customer-facing API's TLS certificate needs controlled renewal before expiration. It is not one of the two requested controls (PIM on-demand roles and Conditional MFA).
Secure secret handling removes reusable credentials from source while preserving automation. Its own validation would be: The committed deployment files contain no functional credentials and the deployment still succeeds. The current paired requirement is PIM on-demand roles and Conditional MFA.
A stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response. The acceptance test is: The scale-in test completes active requests while newly arriving calls use surviving workers. Which design recommendation best satisfies both?
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. The selected architecture is implement connection draining, termination grace periods and readiness controls as supported; confirm the result by checking that the scale-in test completes active requests while newly arriving calls use surviving workers.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. It does not solve the specified Graceful scale-in condition.
Zone redundancy spreads eligible database availability replicas across zones. Its design target is Azure SQL zone redundancy. The stated requirement instead concerns: A stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response.
A zone-separated standby supports automated failover where offered. The relevant requirement is: A stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response.
For the Notification routing requirement, the proposed architecture uses: Attach distinct Azure Monitor action groups to appropriate alert rules. Why does that design fit?
Action groups define notifications and automated responses and can be reused by alert rules. It is material here because critical infrastructure alerts need pager escalation while routine capacity warnings go only to email.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. It belongs to Private observability. The stated architecture instead relies on: Action groups define notifications and automated responses and can be reused by alert rules.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. Action groups define notifications and automated responses and can be reused by alert rules.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Action groups define notifications and automated responses and can be reused by alert rules.
Security leaders need a consolidated assessment against regulatory cloud control baselines. A deployment must satisfy this operational criterion: A noncompliant resource is reported under the relevant regulatory control. Which plan is appropriate?
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The selected architecture is use Microsoft Defender for Cloud regulatory compliance and security posture assessments; confirm the result by checking that a noncompliant resource is reported under the relevant regulatory control.
DeployIfNotExists requires remediation for already deployed resources where appropriate. Its design target is Policy remediation. The stated requirement instead concerns: Security leaders need a consolidated assessment against regulatory cloud control baselines.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. The current need is: Security leaders need a consolidated assessment against regulatory cloud control baselines.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. It does not solve the specified Defender compliance condition.
A solution must address both Policy audit versus deny and RBAC custom role. First requirement: The platform team needs to measure the impact of a new restriction before blocking deployments. Second requirement: A service team needs a narrow set of resource restart and read operations absent from built-in roles. Select TWO recommendations that meet these independent needs.
For the RBAC custom role half of this design, custom role actions can grant specific management operations without broad Contributor rights. Check: The operator restarts an approved service and cannot modify resource access assignments. The other half concerns Policy audit versus deny.
For the Policy audit versus deny half of this two-part design, audit effects collect compliance findings without blocking resource creation. Verify: Noncompliant deployment is logged during pilot but rejected after approved enforcement. The other half concerns RBAC custom role.
Budgets monitor and notify about spending and do not automatically stop resources. This alternative solves Cost budgets, while the question separately requires Policy audit versus deny and RBAC custom role.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Its own validation would be: A noncompliant resource is reported under the relevant regulatory control. The current paired requirement is Policy audit versus deny and RBAC custom role.
Locks prevent specified management operations even for users with broad Azure RBAC roles. This alternative solves Resource locks, while the question separately requires Policy audit versus deny and RBAC custom role.
A short-running event handler reacts to storage events and must scale without provisioned servers. An engineer must deliver the following acceptance evidence: A matching event triggers the function within the required processing window. What design choice is defensible?
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. The selected architecture is use Azure Functions with an event trigger and compatible hosting plan; confirm the result by checking that a matching event triggers the function within the required processing window.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The current need is: A short-running event handler reacts to storage events and must scale without provisioned servers.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. It does not solve the specified Azure Functions event condition.
App Service manages web hosting and supports deployment slots on eligible plans. The relevant requirement is: A short-running event handler reacts to storage events and must scale without provisioned servers.
The acceptance criterion for Front Door rules engine comes from this issue: An application needs to redirect an old URL path and add a security header at the global edge without changing its origin code. Which measured outcome is the strongest proof?
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. Confirm using the measurable result: Requests to the deprecated path redirect and supported responses include the configured header.
Edge caching reduces origin load and latency for eligible cacheable content. The distinguishing check is: Requests to the deprecated path redirect and supported responses include the configured header.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The App Configuration feature flags test checks pilot users see the feature after refresh and others retain the previous behavior; the relevant outcome is Requests to the deprecated path redirect and supported responses include the configured header.
Logic Apps offers managed integration workflows and prebuilt service connectors. The offered observation would demonstrate Logic Apps connector workflow: An approved request creates the expected ticket and notifies the right mailbox. The current validation is different: Requests to the deprecated path redirect and supported responses include the configured header.
An API waits indefinitely for a failing inventory service and exhausts its worker threads. Identify the most suitable implementation for an outcome where simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Failure handling isolates unhealthy dependencies and avoids request pileups. The selected architecture is use timeouts, bounded retries and circuit breaking on downstream calls; confirm the result by checking that simulated downstream failure produces prompt controlled errors while healthy requests remain available.
Edge caching reduces origin load and latency for eligible cacheable content. Its design target is Azure Front Door caching. The stated requirement instead concerns: An API waits indefinitely for a failing inventory service and exhausts its worker threads.
Queueing decouples front-end latency from downstream worker availability. The relevant requirement is: An API waits indefinitely for a failing inventory service and exhausts its worker threads.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. It does not solve the specified Application resilience timeout condition.
Please check your mailbox for a message from support@examlabs.com and follow the directions.