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 acceptance criterion for Azure SQL Database single database comes from this issue: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems. Which measured outcome is the strongest proof?
Azure SQL Database offers fully managed relational database operations with automated backups. Confirm using the measurable result: The application connects through its supported driver without patching database VMs.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. The SQL serverless idle cost test checks compute charges drop during idle periods and the test workload resumes within tolerated delay; the relevant outcome is The application connects through its supported driver without patching database VMs.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The offered observation would demonstrate SQL Server on Azure VM: The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned. The current validation is different: The application connects through its supported driver without patching database VMs.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. The distinguishing check is: The application connects through its supported driver without patching database VMs.
An architect must sign off on Chaos failure testing. The business problem is: A distributed app passes unit tests but its failover behavior under partial dependency loss is unknown. What observed test result provides valid evidence?
Fault injection tests whether resilience patterns work under realistic failure conditions. Confirm using the measurable result: The app maintains the defined availability objective during planned dependency failure.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The offered observation would demonstrate Cosmos multi-write availability: After one region becomes unavailable another authorized region continues to accept writes. The current validation is different: The app maintains the defined availability objective during planned dependency failure.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. The distinguishing check is: The app maintains the defined availability objective during planned dependency failure.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The AKS pod disruption budget test checks a planned node drain leaves the minimum healthy pod count running; the relevant outcome is The app maintains the defined availability objective during planned dependency failure.
A public application must block common HTTP attacks before traffic reaches regional origins worldwide. Identify the most suitable implementation for an outcome where a permitted request reaches its origin while a malicious test pattern is blocked at the edge.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. The selected architecture is attach a supported WAF policy to Azure Front Door routes and validate rule actions; confirm the result by checking that a permitted request reaches its origin while a malicious test pattern is blocked at the edge.
VNet peering alone is not transitive and forwarding needs explicit architecture. The current need is: A public application must block common HTTP attacks before traffic reaches regional origins worldwide.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. It does not solve the specified Front Door WAF edge condition.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. The relevant requirement is: A public application must block common HTTP attacks before traffic reaches regional origins worldwide.
Cloud operations needs eligible administrators to activate subscription Owner only during approved maintenance. The acceptance test is: An eligible operator activates access for the window and loses elevation after expiry. Which design recommendation best satisfies both?
PIM can time-bound eligible role activation with approvals MFA and justification. The selected architecture is configure Privileged Identity Management for Azure resource roles with activation controls; confirm the result by checking that an eligible operator activates access for the window and loses elevation after expiry.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. Its design target is Managed identity for App Service. The stated requirement instead concerns: Cloud operations needs eligible administrators to activate subscription Owner only during approved maintenance.
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. It does not solve the specified PIM on-demand roles condition.
App-only permissions grant service principal operations without a delegated signed-in user. The current need is: Cloud operations needs eligible administrators to activate subscription Owner only during approved maintenance.
Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway. Identify the most suitable implementation for an outcome where a spoke accesses approved hub services and another spoke only through authorized routing.
A hub centralizes connectivity services while spoke VNets isolate applications. The selected architecture is use a hub-and-spoke network topology with shared service governance; confirm the result by checking that a spoke accesses approved hub services and another spoke only through authorized routing.
VPN Gateway can establish encrypted IPsec tunnels over public networks. Its design target is Site-to-site VPN. The stated requirement instead concerns: Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. It does not solve the specified Hub-spoke topology condition.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. That is useful for NSG subnet filtering (A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall). It does not meet the current Hub-spoke topology requirement: Many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway.
A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards. The acceptance test is: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels. Which design recommendation best satisfies both?
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. The selected architecture is enable Azure Monitor managed service for Prometheus for supported Kubernetes clusters; confirm the result by checking that a PromQL dashboard graphs the selected container metric with the expected Kubernetes labels.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. It does not solve the specified Managed Prometheus condition.
Action groups define notifications and automated responses and can be reused by alert rules. That is useful for Notification routing (Critical infrastructure alerts need pager escalation while routine capacity warnings go only to email). It does not meet the current Managed Prometheus requirement: A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards.
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: A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards.
Architecture review: Subscription isolation and Policy exclusion scope. Requirement A: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit. Requirement B: One application needs a carefully controlled exception to a management group policy. Which complete two-part proposal satisfies both constraints?
For requirement A, subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. For requirement B, policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. Verify both independently: The subsidiary's budget and policy reports stay distinct from the parent; Only the approved application scope avoids the specified policy effect.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. The proposed steps (check subscription and regional service quotas before architecture signoff and request increases; build a management-group hierarchy with appropriate policy and RBAC inheritance) address other capabilities instead of this required pair.
The mismatched half is Management group hierarchy; Policy exclusion scope instead needs: Use scoped policy exemptions or exclusion with documented rationale and review.
The first step implements Quotas and limits instead of Subscription isolation. The necessary change is to place regulated workloads in designated subscriptions under suitable management groups.
The App Service zone redundancy review proposes: Use a supported zone-redundant App Service plan with adequate instances. Which Azure behavior is the technical justification for this decision?
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. It is material here because a production App Service must resist a zone failure without managing VM instances.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. It belongs to Traffic Manager DNS routing. The stated architecture instead relies on: Eligible App Service plans distribute app workers across availability zones with sufficient capacity.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. That statement describes Zone-redundant load balancer, while the question asks how App Service zone redundancy works: Eligible App Service plans distribute app workers across availability zones with sufficient capacity.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. Eligible App Service plans distribute app workers across availability zones with sufficient capacity.
During technical sign-off for Azure SQL zone redundancy, the architect selects: Choose a supported zone-redundant Azure SQL tier and configuration. Which underlying behavior should be documented?
Zone redundancy spreads eligible database availability replicas across zones. It is material here because a transactional SQL database must withstand a full zone failure with minimal manual intervention.
Availability zones isolate infrastructure failure domains within an enabled region. Zone redundancy spreads eligible database availability replicas across zones.
Fault injection tests whether resilience patterns work under realistic failure conditions. Zone redundancy spreads eligible database availability replicas across zones.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. It belongs to Application Gateway zone redundancy. The stated architecture instead relies on: Zone redundancy spreads eligible database availability replicas across zones.
Architecture rationale review—Managed identity for App Service: Enable a managed identity and grant it Storage Blob Data Reader at the smallest needed scope. Which explanation accurately distinguishes this capability?
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. It is material here because a web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. It belongs to Vault network boundary. The stated architecture instead relies on: Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions.
Key Vault keys can perform cryptographic operations while restricting private key exposure. That statement describes Key Vault cryptographic signing, while the question asks how Managed identity for App Service works: Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions.
For Cross-tenant operations, operations are closing a change that addressed: An MSP needs delegated visibility into customer Azure resource monitoring without separate customer logins. Which post-change signal belongs in the acceptance record?
Lighthouse enables delegated management across tenants without relocating customer-owned resources. Confirm using the measurable result: Authorized MSP operators view the delegated customer's resource health from their managing tenant.
Resource Health reports the platform-side availability history of individual Azure resources. Those observations validate VM resource health. They do not establish the required Cross-tenant operations result: Authorized MSP operators view the delegated customer's resource health from their managing tenant.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. The distinguishing check is: Authorized MSP operators view the delegated customer's resource health from their managing tenant.
DCRs specify collected streams destinations and transformations for supported agent sources. The offered observation would demonstrate Agent collection rules: Production servers send approved counters while test servers omit the excluded stream. The current validation is different: Authorized MSP operators view the delegated customer's resource health from their managing tenant.
Please check your mailbox for a message from support@examlabs.com and follow the directions.