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 App Service web. Its governing requirement was: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Identify the conclusive verification result.
App Service manages web hosting and supports deployment slots on eligible plans. Confirm using the measurable result: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
VMSS automates management and scaling of similar VMs in the same workload. Those observations validate VMSS dynamic scaling. They do not establish the required App Service web result: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
GPU instances provide accelerators not present on standard CPU-only VMs. The distinguishing check is: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
Encryption sets connect managed disk encryption to customer-owned keys. The offered observation would demonstrate VM disk encryption: Disk configuration shows the designated key and encrypted state before production traffic. The current validation is different: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
Architecture rationale review—PostgreSQL PITR: Use Flexible Server point-in-time restore within supported backup-retention limits. Which explanation accurately distinguishes this capability?
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. It is material here because a managed PostgreSQL server is damaged by a schema update and needs its prior state.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. It belongs to Backup private endpoints. The stated architecture instead relies on: Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time.
Architecture review: NAT Gateway outbound and NSG subnet filtering. Requirement A: A subnet-based worker fleet needs stable outbound public IPs without per-VM public IP addresses. Requirement B: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall. Which complete two-part proposal satisfies both constraints?
For requirement A, NAT Gateway provides outbound SNAT for supported subnet internet traffic. For requirement B, nSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Verify both independently: External partners observe only the approved outbound IP during simultaneous worker sessions; The approved source reaches TCP 443 and another source is denied.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. The proposed steps (design a routing/transit solution with a supported NVA or Azure Firewall where required; use Azure Route Server to exchange BGP routes with a supported NVA) address other capabilities instead of this required pair.
The first step implements Peering nontransitivity instead of NAT Gateway outbound. The necessary change is to attach a NAT Gateway to the worker subnet with the approved public IP resources.
One action is correct. The other targets Route Server dynamic routing, leaving NSG subnet filtering unsolved. Its necessary action is: Apply NSG rules at an appropriate subnet or NIC scope.
The platform team needs to measure the impact of a new restriction before blocking deployments. Identify the most suitable implementation for an outcome where noncompliant deployment is logged during pilot but rejected after approved enforcement.
Audit effects collect compliance findings without blocking resource creation. The selected architecture is roll out an Azure Policy rule initially with audit then switch to deny after remediation; confirm the result by checking that noncompliant deployment is logged during pilot but rejected after approved enforcement.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The current need is: The platform team needs to measure the impact of a new restriction before blocking deployments.
Modify effects can update eligible metadata and require the required remediation permissions. It does not solve the specified Policy audit versus deny condition.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Its design target is Management group hierarchy. The stated requirement instead concerns: The platform team needs to measure the impact of a new restriction before blocking deployments.
A solution must address both Vault immutability and Multifactor critical operations. First requirement: A security audit worries a compromised backup administrator could delete protected recovery points. Second requirement: Ransomware attackers should not disable backup protection with a single compromised admin account. Select TWO recommendations that meet these independent needs.
For the Multifactor critical operations half of this design, multi-user authorization separates approval boundaries for critical backup changes. Check: A destructive backup operation requires the independent authorized role. The other half concerns Vault immutability.
For the Vault immutability half of this two-part design, immutable backup settings can prevent specified destructive operations against protected backups. Verify: A forbidden backup deletion or retention reduction is rejected during the configured protection period. The other half concerns Multifactor critical operations.
Nightly backups alone do not provide continuous workload replication or low recovery time. That plan is appropriate for Backup versus DR. The two controls sought here are Vault immutability and Multifactor critical operations.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. Its own validation would be: A restored database contains transactions immediately preceding the truncation. The current paired requirement is Vault immutability and Multifactor critical operations.
Failback is a separate operational sequence after workloads run in the recovery site. This alternative solves Failback after recovery, while the question separately requires Vault immutability and Multifactor critical operations.
A billing workflow needs durable work messages with transactions, sessions and dead-letter handling. An architecture board will approve a solution only if this outcome is demonstrated: A poison message moves to the dead-letter queue while ordered session items retain their sequence. What should be selected?
Service Bus is an enterprise message broker with delivery and dead-letter semantics. The selected architecture is use Azure Service Bus queues/topics with sessions when ordered processing is required; confirm the result by checking that a poison message moves to the dead-letter queue while ordered session items retain their sequence.
Tumbling-window triggers model contiguous time slices with support for backfill. It does not solve the specified Service Bus ordering condition.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. The relevant requirement is: A billing workflow needs durable work messages with transactions, sessions and dead-letter handling.
Self-hosted integration runtime initiates supported outbound communications to access private sources. The current need is: A billing workflow needs durable work messages with transactions, sessions and dead-letter handling.
Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture. Which Azure architecture would most directly achieve the required result: A blocked test connection is correlated with its source destination and flow disposition?
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. The selected architecture is configure supported virtual network flow logs with Traffic Analytics where available; confirm the result by checking that a blocked test connection is correlated with its source destination and flow disposition.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Its design target is Immutable evidence archive. The stated requirement instead concerns: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture.
Action groups define notifications and automated responses and can be reused by alert rules. The current need is: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture.
DCRs specify collected streams destinations and transformations for supported agent sources. It does not solve the specified Network-flow telemetry condition.
Architecture review: Point-to-site VPN and Site-to-site VPN. Requirement A: Remote administrators need individually authenticated encrypted connectivity to Azure private resources. Requirement B: A small branch needs encrypted connectivity to a VNet over its existing internet link. Which complete two-part proposal satisfies both constraints?
For requirement A, point-to-site VPN authenticates individual clients for private network access. For requirement B, VPN Gateway can establish encrypted IPsec tunnels over public networks. Verify both independently: Authorized clients connect privately and revoked clients cannot establish a tunnel; Encrypted traffic reaches the approved private Azure subnet from the branch.
The first step implements DDoS protection instead of Point-to-site VPN. The necessary change is to use Azure VPN Gateway point-to-site with an appropriate identity provider.
The option covers one requirement but substitutes Front Door WAF edge for Site-to-site VPN. The missing acceptance result is: Encrypted traffic reaches the approved private Azure subnet from the branch.
Point-to-site VPN authenticates individual clients for private network access. VPN Gateway can establish encrypted IPsec tunnels over public networks. The proposed steps (evaluate Azure DDoS Network Protection for eligible public IPs and VNets; attach a supported WAF policy to Azure Front Door routes and validate rule actions) address other capabilities instead of this required pair.
An architect must sign off on SQL database partitioning. The business problem is: A large transaction table suffers scans on historical data and needs time-based management. What observed test result provides valid evidence?
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. Confirm using the measurable result: Execution plans prune irrelevant historical partitions for the test query.
Migration assessment identifies blockers and target-fit issues before a cutover. The distinguishing check is: Execution plans prune irrelevant historical partitions for the test query.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. The SQL database monitoring test checks top resource-consuming queries and resource-limit events are visible during peak load; the relevant outcome is Execution plans prune irrelevant historical partitions for the test query.
Temporal tables retain row history and support as-of queries independently of whole-database backups. The offered observation would demonstrate SQL temporal tables: An as-of query reconstructs the record before an approved change. The current validation is different: Execution plans prune irrelevant historical partitions for the test query.
Architecture review: Cosmos DB NoSQL and Cosmos partition key. Requirement A: A globally distributed app stores schemaless JSON records at high scale with flexible document queries. Requirement B: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling. Which complete two-part proposal satisfies both constraints?
For requirement A, Cosmos DB provides a distributed document database with configurable consistency and throughput. For requirement B, partition key distribution governs data/throughput placement and query efficiency. Verify both independently: The app reads JSON documents across the planned partitions with predictable latency; RU consumption distributes across partitions and the query includes its expected partition key.
Cosmos DB provides a distributed document database with configurable consistency and throughput. Partition key distribution governs data/throughput placement and query efficiency. The proposed steps (enable hierarchical namespace and use Azure Data Lake Storage Gen2 capabilities; evaluate Premium SSD v2 managed disks where region and VM support permit) address other capabilities instead of this required pair.
The first step implements Blob HNS namespace instead of Cosmos DB NoSQL. The necessary change is to choose Azure Cosmos DB for NoSQL with suitable partition and consistency design.
The option covers one requirement but substitutes Premium SSD v2 for Cosmos partition key. The missing acceptance result is: RU consumption distributes across partitions and the query includes its expected partition key.
A workload requires write access to one blob container but must not inherit owner rights over the subscription. Choose the architecture that can be validated by this result: Container writes succeed while administrative ownership actions remain denied.
Data-plane roles control access to blob content and least-scope assignment reduces unnecessary privileges. The selected architecture is grant a suitable storage data role at the narrow supported resource scope; confirm the result by checking that container writes succeed while administrative ownership actions remain denied.
Authentication strengths let Conditional Access require supported strong methods based on conditions. Its design target is Conditional MFA. The stated requirement instead concerns: A workload requires write access to one blob container but must not inherit owner rights over the subscription.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. It does not solve the specified Managed-identity scope condition.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. That is useful for Managed identity for App Service (A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings). It does not meet the current Managed-identity scope requirement: A workload requires write access to one blob container but must not inherit owner rights over the subscription.
Please check your mailbox for a message from support@examlabs.com and follow the directions.