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
Remote administrators need individually authenticated encrypted connectivity to Azure private resources. Choose the architecture that can be validated by this result: Authorized clients connect privately and revoked clients cannot establish a tunnel.
Point-to-site VPN authenticates individual clients for private network access. The selected architecture is use Azure VPN Gateway point-to-site with an appropriate identity provider; confirm the result by checking that authorized clients connect privately and revoked clients cannot establish a tunnel.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. It does not solve the specified Point-to-site VPN condition.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. That is useful for VNet peering (Two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways). It does not meet the current Point-to-site VPN requirement: Remote administrators need individually authenticated encrypted connectivity to Azure private resources.
VPN Gateway can establish encrypted IPsec tunnels over public networks. The relevant requirement is: Remote administrators need individually authenticated encrypted connectivity to Azure private resources.
A rollout addressing Azure Migrate inventory has reached acceptance testing. The original problem was: An on-prem estate has hundreds of VMs and architects need dependency-aware discovery before sizing Azure. Which finding verifies its resolution?
Azure Migrate inventories servers and supports readiness and sizing assessments. Confirm using the measurable result: Assessment lists discovered servers, interdependencies and estimated Azure sizing.
PostgreSQL migration requires extension, version and connectivity compatibility checks. The PostgreSQL migration test checks the database app passes read/write tests against the target flexible server; the relevant outcome is Assessment lists discovered servers, interdependencies and estimated Azure sizing.
Offline migration can simplify cutover when application downtime is acceptable. The offered observation would demonstrate SQL offline migration: The migrated database passes consistency checks before reopening writes. The current validation is different: Assessment lists discovered servers, interdependencies and estimated Azure sizing.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Those observations validate Storage bulk offline transfer. They do not establish the required Azure Migrate inventory result: Assessment lists discovered servers, interdependencies and estimated Azure sizing.
A solution must address both DDoS protection and NAT Gateway outbound. First requirement: A publicly reachable application needs additional DDoS mitigation beyond basic platform protections. Second requirement: A subnet-based worker fleet needs stable outbound public IPs without per-VM public IP addresses. Select TWO recommendations that meet these independent needs.
For the DDoS protection half of this two-part design, dDoS protection adds adaptive mitigation and telemetry for supported public resources. Verify: Protection coverage reports the eligible public IP and test telemetry is available. The other half concerns NAT Gateway outbound.
For the NAT Gateway outbound half of this design, NAT Gateway provides outbound SNAT for supported subnet internet traffic. Check: External partners observe only the approved outbound IP during simultaneous worker sessions. The other half concerns DDoS protection.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Its own validation would be: A test workload reaches Azure over advertised private prefixes when one circuit path fails. The current paired requirement is DDoS protection and NAT Gateway outbound.
VPN Gateway can establish encrypted IPsec tunnels over public networks. This alternative solves Site-to-site VPN, while the question separately requires DDoS protection and NAT Gateway outbound.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. Its own validation would be: Private IP traffic flows between the peered VNets with appropriate NSG permissions. The current paired requirement is DDoS protection and NAT Gateway outbound.
Architecture rationale review—Zone-redundant load balancer: Use a supported zone-redundant Standard Load Balancer deployment with health probes. Which explanation accurately distinguishes this capability?
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. It is material here because a regional application needs one L4 frontend distributing traffic to healthy VMs across zones.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests.
Failover-group listeners abstract the primary location during regional failover. Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests.
Read regions bring replicas closer to users without inherently adding multi-write semantics. That statement describes Cosmos multi-region reads, while the question asks how Zone-redundant load balancer works: Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests.
A solution must address both PostgreSQL PITR and SQL database PITR. First requirement: A managed PostgreSQL server is damaged by a schema update and needs its prior state. Second requirement: A deployment accidentally truncates a transaction table and the database must be recovered before the change. Select TWO recommendations that meet these independent needs.
For the PostgreSQL PITR half of this two-part design, managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. Verify: A recovered server answers queries using data from before the accidental update. The other half concerns SQL database PITR.
For the SQL database PITR half of this design, Azure SQL automatic full differential and log backups support restoring database state at a selected time. Check: A restored database contains transactions immediately preceding the truncation. The other half concerns PostgreSQL PITR.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. The corresponding task is Cross-region backup: An organization requires VM backup copies surviving the loss of an entire Azure region. It is not one of the two requested controls (PostgreSQL PITR and SQL database PITR).
Backup-specific RBAC roles separate operational restore tasks from vault administration. That plan is appropriate for Backup vault access. The two controls sought here are PostgreSQL PITR and SQL database PITR.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. This alternative solves Blob operational backup, while the question separately requires PostgreSQL PITR and SQL database PITR.
Architecture review: Azure Files snapshots and Backup soft delete. Requirement A: An Azure Files SMB share needs hourly recovery of files accidentally overwritten by users. Requirement B: An operator deletes a backup item by mistake and must recover its protected points before permanent purge. Which complete two-part proposal satisfies both constraints?
For requirement A, share snapshots preserve file-share point-in-time state for supported restoration. For requirement B, soft delete retains recoverable protected backup data after deletion for a configured interval. Verify both independently: An earlier version of an overwritten spreadsheet is recovered from a share snapshot; The deleted item is recoverable within the protected deletion window.
Share snapshots preserve file-share point-in-time state for supported restoration. Soft delete retains recoverable protected backup data after deletion for a configured interval. The proposed steps (assign scoped backup roles with least privilege and protected operation controls; use supported blob operational backup with versioning and change feed prerequisites) address other capabilities instead of this required pair.
The first step implements Backup vault access instead of Azure Files snapshots. The necessary change is to use Azure Files share snapshots and an appropriate Azure Backup policy if needed.
The option covers one requirement but substitutes Blob operational backup for Backup soft delete. The missing acceptance result is: The deleted item is recoverable within the protected deletion window.
A solution must address both SQL migration assessment and SQL managed instance compatibility. First requirement: A legacy SQL database contains unsupported features and the team wants a target tier before moving. Second requirement: A legacy SQL Server app requires SQL Agent jobs and broad instance-level compatibility during cloud migration. Select TWO recommendations that meet these independent needs.
For the SQL managed instance compatibility half of this design, managed Instance supports many instance-scoped SQL Server capabilities with a managed service. Check: Compatibility assessment and agent-dependent workloads complete without rewriting required instance features. The other half concerns SQL migration assessment.
For the SQL migration assessment half of this two-part design, migration assessment identifies blockers and target-fit issues before a cutover. Verify: The compatibility report has no unmitigated blocking features for the chosen target. The other half concerns SQL managed instance compatibility.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. Its own validation would be: Top resource-consuming queries and resource-limit events are visible during peak load. The current paired requirement is SQL migration assessment and SQL managed instance compatibility.
Flexible Server provides managed MySQL compute storage and backups. The corresponding task is MySQL managed service: An existing MySQL application needs automated patching and backups with minimal database changes. It is not one of the two requested controls (SQL migration assessment and SQL managed instance compatibility).
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. That plan is appropriate for PostgreSQL flexible server. The two controls sought here are SQL migration assessment and SQL managed instance compatibility.
A finance VM needs customer-managed encryption keys for managed disks. An architecture board will approve a solution only if this outcome is demonstrated: Disk configuration shows the designated key and encrypted state before production traffic. What should be selected?
Encryption sets connect managed disk encryption to customer-owned keys. The selected architecture is use supported disk encryption-set customer-managed keys with suitable identity and vault; confirm the result by checking that disk configuration shows the designated key and encrypted state before production traffic.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. The relevant requirement is: A finance VM needs customer-managed encryption keys for managed disks.
Spot instances offer lower-priced spare capacity without guaranteed availability. It does not solve the specified VM disk encryption condition.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. Its design target is Autoscaling based on queue. The stated requirement instead concerns: A finance VM needs customer-managed encryption keys for managed disks.
For Defender compliance, operations are closing a change that addressed: Security leaders need a consolidated assessment against regulatory cloud control baselines. Which post-change signal belongs in the acceptance record?
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Confirm using the measurable result: A noncompliant resource is reported under the relevant regulatory control.
Policy evaluates resource deployment properties and rejects noncompliant regions. Those observations validate Allowed regions. They do not establish the required Defender compliance result: A noncompliant resource is reported under the relevant regulatory control.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. The distinguishing check is: A noncompliant resource is reported under the relevant regulatory control.
Custom role actions can grant specific management operations without broad Contributor rights. The RBAC custom role test checks the operator restarts an approved service and cannot modify resource access assignments; the relevant outcome is A noncompliant resource is reported under the relevant regulatory control.
Before approving Web PubSub real time, the reviewer assesses this requirement: A collaboration app must send real-time server-to-client notifications to many concurrent browsers. Which of the reported outcomes is decisive?
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. Confirm using the measurable result: Two connected clients immediately receive the authorized published event.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. The distinguishing check is: Two connected clients immediately receive the authorized published event.
At-least-once message delivery requires application logic to deduplicate business side effects. The Reliable exactly-once effect test checks two deliveries of the same order ID create only one invoice; the relevant outcome is Two connected clients immediately receive the authorized published event.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The offered observation would demonstrate Front Door rules engine: Requests to the deprecated path redirect and supported responses include the configured header. The current validation is different: Two connected clients immediately receive the authorized published event.
Operators must turn a feature on for a pilot group without rebuilding application binaries. The acceptance test is: Pilot users see the feature after refresh and others retain the previous behavior. Which design recommendation best satisfies both?
App Configuration centralizes feature settings; secrets should remain in Key Vault. The selected architecture is store nonsecret feature flags in Azure App Configuration with app-side refresh; confirm the result by checking that pilot users see the feature after refresh and others retain the previous behavior.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The relevant requirement is: Operators must turn a feature on for a pilot group without rebuilding application binaries.
Edge content distribution can cache static resources near users. It does not solve the specified App Configuration feature flags condition.
Asynchronous projections can lag writes and need clear read-after-write expectations. That is useful for Eventual consistency UX (An order service writes asynchronously into a read model and users momentarily see old data). It does not meet the current App Configuration feature flags requirement: Operators must turn a feature on for a pilot group without rebuilding application binaries.
Please check your mailbox for a message from support@examlabs.com and follow the directions.