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 web workload requires HTTP routing and WAF across availability zones. An architecture board will approve a solution only if this outcome is demonstrated: The gateway keeps HTTP traffic flowing when a backend zone is unavailable. What should be selected?
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. The selected architecture is use a supported zone-redundant Application Gateway WAF tier; confirm the result by checking that the gateway keeps HTTP traffic flowing when a backend zone is unavailable.
Transient-failure handling reduces unnecessary outages while preventing retry storms. The current need is: A web workload requires HTTP routing and WAF across availability zones.
Fault injection tests whether resilience patterns work under realistic failure conditions. Its design target is Chaos failure testing. The stated requirement instead concerns: A web workload requires HTTP routing and WAF across availability zones.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. It does not solve the specified Application Gateway zone redundancy condition.
Architecture review: Managed Prometheus and VM guest performance. Requirement A: A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards. Requirement B: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics. Which complete two-part proposal satisfies both constraints?
For requirement A, managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. For requirement B, VM insights and the agent collect supported guest operating-system counters and process data. Verify both independently: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels; Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
One action is correct. The other targets WAF decision logs, leaving VM guest performance unsolved. Its necessary action is: Enable VM insights with the Azure Monitor Agent and appropriate data collection rule.
VM insights and the agent collect supported guest operating-system counters and process data. The other proposed action (enable the supported SQL resource diagnostic categories to a Log Analytics workspace) does not implement the first control. Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection.
Both proposed halves address other use cases: Database resource diagnostics and WAF decision logs. The requested pair is Managed Prometheus and VM guest performance.
Architecture review: AKS pod disruption budget and AKS availability zones. Requirement A: Cluster upgrades evict all replicas of an API despite multiple healthy nodes. 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, pDBs constrain voluntary disruptions but do not prevent all involuntary failures. For requirement B, zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. Verify both independently: A planned node drain leaves the minimum healthy pod count running; After a simulated zone failure, surviving pods maintain API availability and replacement replicas become Ready within the tested recovery window on healthy-zone nodes.
Zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. The other proposed action (configure Azure SQL failover groups and an app connection using the appropriate listener) does not implement the first control. PDBs constrain voluntary disruptions but do not prevent all involuntary failures.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. The other proposed action (select GZRS or RA-GZRS based on read access needs and service support) addresses a different operation. Zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration.
Both proposed halves address other use cases: SQL failover groups HA and Blob GZRS durability. The requested pair is AKS pod disruption budget and AKS availability zones.
Architecture review: Backup soft delete and Vault immutability. Requirement A: An operator deletes a backup item by mistake and must recover its protected points before permanent purge. Requirement B: A security audit worries a compromised backup administrator could delete protected recovery points. Which complete two-part proposal satisfies both constraints?
For requirement A, soft delete retains recoverable protected backup data after deletion for a configured interval. For requirement B, immutable backup settings can prevent specified destructive operations against protected backups. Verify both independently: The deleted item is recoverable within the protected deletion window; A forbidden backup deletion or retention reduction is rejected during the configured protection period.
Both proposed halves address other use cases: Backup private endpoints and Blob vaulted backup. The requested pair is Backup soft delete and Vault immutability.
One action is correct. The other targets Blob vaulted backup, leaving Vault immutability unsolved. Its necessary action is: Enable an appropriately configured immutable Azure Backup vault with supporting controls.
Immutable backup settings can prevent specified destructive operations against protected backups. The other proposed action (use approved private endpoint configuration for the supported backup scenario) does not implement the first control. Soft delete retains recoverable protected backup data after deletion for a configured interval.
For Circuit breaker behavior, operations are closing a change that addressed: A downstream service stays unhealthy and unlimited client retries exhaust all front-end worker threads. Which post-change signal belongs in the acceptance record?
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. Confirm using the measurable result: Unhealthy requests fail quickly and the service resumes calls after recovery.
Failover-group listeners abstract the primary location during regional failover. Those observations validate SQL failover groups HA. They do not establish the required Circuit breaker behavior result: Unhealthy requests fail quickly and the service resumes calls after recovery.
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 Unhealthy requests fail quickly and the service resumes calls after recovery.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. The offered observation would demonstrate Availability set: A planned host update does not make every VM unavailable at once. The current validation is different: Unhealthy requests fail quickly and the service resumes calls after recovery.
The team has justified its Secrets in deployment pipeline design with: Use secure parameter references and retrieve protected values from an approved secret store. Which statement accurately describes why the approach works?
Secure secret handling removes reusable credentials from source while preserving automation. It is material here because an IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. That statement describes Consumer sign-in, while the question asks how Secrets in deployment pipeline works: Secure secret handling removes reusable credentials from source while preserving automation.
App-only permissions grant service principal operations without a delegated signed-in user. Secure secret handling removes reusable credentials from source while preserving automation.
Delegated permissions represent what an application can do on behalf of an authenticated user. Secure secret handling removes reusable credentials from source while preserving automation.
An in-memory analytics engine repeatedly pages memory on a standard VM size. Choose the architecture that can be validated by this result: Paging falls and the working data fits within the selected RAM capacity.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. The selected architecture is select a memory-optimized Azure VM family after measuring peak resident memory; confirm the result by checking that paging falls and the working data fits within the selected RAM capacity.
Compute Gallery distributes managed image versions for repeatable VM deployments. The relevant requirement is: An in-memory analytics engine repeatedly pages memory on a standard VM size.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. It does not solve the specified Memory optimized VM condition.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That is useful for App Service isolation (A regulated web application needs private dedicated hosting and stricter network isolation). It does not meet the current Memory optimized VM requirement: An in-memory analytics engine repeatedly pages memory on a standard VM size.
An architect must sign off on Azure VM backup policy. The business problem is: A production Azure VM must be recoverable to an earlier day after accidental deletion of application files. What observed test result provides valid evidence?
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. Confirm using the measurable result: A file-level restore recovers the deleted content from the appropriate recovery point.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The offered observation would demonstrate Recovery drill governance: The test network runs recovered workloads and production endpoints remain unaffected. The current validation is different: A file-level restore recovers the deleted content from the appropriate recovery point.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. The distinguishing check is: A file-level restore recovers the deleted content from the appropriate recovery point.
Multi-user authorization separates approval boundaries for critical backup changes. The Multifactor critical operations test checks a destructive backup operation requires the independent authorized role; the relevant outcome is A file-level restore recovers the deleted content from the appropriate recovery point.
A proposed solution for Point-to-site VPN is: Use Azure VPN Gateway point-to-site with an appropriate identity provider. Select the strongest statement supporting the recommendation.
Point-to-site VPN authenticates individual clients for private network access. It is material here because remote administrators need individually authenticated encrypted connectivity to Azure private resources.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. It belongs to ExpressRoute private circuit. The stated architecture instead relies on: Point-to-site VPN authenticates individual clients for private network access.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. That statement describes Service endpoint, while the question asks how Point-to-site VPN works: Point-to-site VPN authenticates individual clients for private network access.
Private DNS zone links determine name resolution for VNets that consume private endpoints. Point-to-site VPN authenticates individual clients for private network access.
A database handles patient identifiers that should stay encrypted from database administrators during normal access. Choose the architecture that can be validated by this result: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. The selected architecture is use SQL Always Encrypted with appropriate key management and compatible client drivers; confirm the result by checking that the client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. That is useful for SQL geo-replication reporting (A geographically distributed app needs a readable secondary SQL database to offload reports without moving the primary write location). It does not meet the current SQL Always Encrypted requirement: A database handles patient identifiers that should stay encrypted from database administrators during normal access.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. It does not solve the specified SQL Always Encrypted condition.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. The current need is: A database handles patient identifiers that should stay encrypted from database administrators during normal access.
A rendering workload can checkpoint and tolerate eviction but has a tight compute budget. An architecture board will approve a solution only if this outcome is demonstrated: An eviction event restarts work from its last saved checkpoint on available capacity. What should be selected?
Spot instances offer lower-priced spare capacity without guaranteed availability. The selected architecture is use Azure Spot VMs with checkpointing and capacity-aware fallback; confirm the result by checking that an eviction event restarts work from its last saved checkpoint on available capacity.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. It does not solve the specified Spot VM suitability condition.
GPU instances provide accelerators not present on standard CPU-only VMs. The current need is: A rendering workload can checkpoint and tolerate eviction but has a tight compute budget.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That is useful for App Service isolation (A regulated web application needs private dedicated hosting and stricter network isolation). It does not meet the current Spot VM suitability requirement: A rendering workload can checkpoint and tolerate eviction but has a tight compute budget.
Please check your mailbox for a message from support@examlabs.com and follow the directions.