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
Before approving Agent collection rules, the reviewer assesses this requirement: Windows servers send performance counters that should differ by workload and environment. Which of the reported outcomes is decisive?
DCRs specify collected streams destinations and transformations for supported agent sources. Confirm using the measurable result: Production servers send approved counters while test servers omit the excluded stream.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The Immutable evidence archive test checks a retained log blob rejects unauthorized deletion during its compliance retention window; the relevant outcome is Production servers send approved counters while test servers omit the excluded stream.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Those observations validate Azure service health. They do not establish the required Agent collection rules result: Production servers send approved counters while test servers omit the excluded stream.
Analytics and longer-term retention options have different query and storage cost characteristics. The distinguishing check is: Production servers send approved counters while test servers omit the excluded stream.
A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems. Which Azure architecture would most directly achieve the required result: The application connects through its supported driver without patching database VMs?
Azure SQL Database offers fully managed relational database operations with automated backups. The selected architecture is select Azure SQL Database for the managed individual database; confirm the result by checking that the application connects through its supported driver without patching database VMs.
Migration assessment identifies blockers and target-fit issues before a cutover. It does not solve the specified Azure SQL Database single database condition.
Hyperscale decouples storage scale from compute and supports large database sizes. That is useful for SQL Hyperscale growth (One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers). It does not meet the current Azure SQL Database single database requirement: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. Its design target is SQL managed instance compatibility. The stated requirement instead concerns: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems.
The Conditional MFA review proposes: Apply a Conditional Access policy with an appropriate authentication strength to privileged roles. Which Azure behavior is the technical justification for this decision?
Authentication strengths let Conditional Access require supported strong methods based on conditions. It is material here because administrators must use phishing-resistant authentication for high-privilege cloud portal actions.
PIM can time-bound eligible role activation with approvals MFA and justification. Authentication strengths let Conditional Access require supported strong methods based on conditions.
Delegated permissions represent what an application can do on behalf of an authenticated user. That statement describes App registration API scopes, while the question asks how Conditional MFA works: Authentication strengths let Conditional Access require supported strong methods based on conditions.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. Authentication strengths let Conditional Access require supported strong methods based on conditions.
Architecture rationale review—GPU VM: Use an Azure GPU-capable VM family compatible with the model runtime. Which explanation accurately distinguishes this capability?
GPU instances provide accelerators not present on standard CPU-only VMs. It is material here because a model inference service needs supported GPU acceleration and low response latency.
ASE provides dedicated App Service hosting in a customer virtual-network environment. It belongs to App Service isolation. The stated architecture instead relies on: GPU instances provide accelerators not present on standard CPU-only VMs.
Blue-green deployment preserves a prior known-good instance while testing a replacement. GPU instances provide accelerators not present on standard CPU-only VMs.
Redundancy prevents a single host maintenance event from removing the only serving instance. GPU instances provide accelerators not present on standard CPU-only VMs.
An engineer only operates one network resource group but has Contributor for the whole subscription. Choose the architecture that can be validated by this result: The engineer can change the assigned network group but not another group's resources.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The selected architecture is remove broad role inheritance and grant least-scope RBAC at the resource-group boundary; confirm the result by checking that the engineer can change the assigned network group but not another group's resources.
Policy exemptions record approved exceptions while the policy remains assigned. The relevant requirement is: An engineer only operates one network resource group but has Contributor for the whole subscription.
Policy deny or audit effects can enforce required metadata at supported resource scopes. It does not solve the specified Role assignment scope condition.
Infrastructure as code declares desired resources and allows review and repeat deployment. That is useful for Standardized IaC (Operations wants reproducible Azure environment deployments from version-controlled definitions). It does not meet the current Role assignment scope requirement: An engineer only operates one network resource group but has Contributor for the whole subscription.
An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health. Which Azure architecture would most directly achieve the required result: The restarting pod and its container events are visible with node and namespace context?
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. The selected architecture is configure Container insights for the supported AKS cluster logging and telemetry; confirm the result by checking that the restarting pod and its container events are visible with node and namespace context.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. It does not solve the specified AKS container diagnosis condition.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The current need is: An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health.
KQL summarizes timestamped structured log data across dimensions such as operation and cloud role. That is useful for Error trend queries (Operations must aggregate intermittent HTTP 500s by service and hour from application traces). It does not meet the current AKS container diagnosis requirement: An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health.
Architecture review: VM disk encryption and App Service web. Requirement A: A finance VM needs customer-managed encryption keys for managed disks. Requirement B: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Which complete two-part proposal satisfies both constraints?
For requirement A, encryption sets connect managed disk encryption to customer-owned keys. For requirement B, App Service manages web hosting and supports deployment slots on eligible plans. Verify both independently: Disk configuration shows the designated key and encrypted state before production traffic; Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
The option covers one requirement but substitutes Azure Functions durable workflow for App Service web. The missing acceptance result is: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
One action is correct. The other targets Azure Functions event, leaving VM disk encryption unsolved. Its necessary action is: Use supported disk encryption-set customer-managed keys with suitable identity and vault.
Encryption sets connect managed disk encryption to customer-owned keys. App Service manages web hosting and supports deployment slots on eligible plans. The proposed steps (use Azure Functions with an event trigger and compatible hosting plan; use Durable Functions orchestration with proper idempotent activity design) address other capabilities instead of this required pair.
A multi-tenant API must protect its backend from brief request spikes. One client sometimes sends more requests than its approved short-window allowance, while other clients must retain access. The acceptance test sends a controlled burst above the per-client rate and verifies that API Management returns HTTP 429 for the excess while allowing the permitted requests. Which configuration most directly supplies this burst-rate control?
The APIM rate-limit-by-key policy throttles short bursts by applying a per-key request counter, call allowance and renewal period at a supported policy scope. It returns HTTP 429 when the rate is exceeded. A test must verify the intended client key is used, permitted calls proceed and a high-volume burst yields throttling, with allowance for small distributed-counter variation; this is distinct from a longer-term quota that commonly returns HTTP 403.
Placing API Management in front of the backend creates the policy enforcement point but does not itself set an inbound per-client rate counter or request threshold. The requested burst test needs a configured rate-limit policy; gateway placement alone cannot prove 429 throttling.
Azure CDN or Front Door static asset distribution can improve edge delivery and caching but does not configure a per-client short-window inbound call-rate threshold on the protected API. It cannot establish the required 429 burst response.
Event Hubs partitions and consumer groups organize stream ingestion and replay. They do not implement an inbound HTTP API rate limit keyed to the request client, so they cannot prove burst throttling at the API Management gateway.
A global application must continue accepting writes from multiple regions when one region fails. Choose the architecture that can be validated by this result: After one region becomes unavailable another authorized region continues to accept writes.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The selected architecture is consider Cosmos DB multi-region writes with conflict-resolution design; confirm the result by checking that after one region becomes unavailable another authorized region continues to accept writes.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. It does not solve the specified Cosmos multi-write availability condition.
Availability zones isolate infrastructure failure domains within an enabled region. The current need is: A global application must continue accepting writes from multiple regions when one region fails.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. That is useful for Zone-redundant load balancer (A regional application needs one L4 frontend distributing traffic to healthy VMs across zones). It does not meet the current Cosmos multi-write availability requirement: A global application must continue accepting writes from multiple regions when one region fails.
The target environment adopts this approach for Cosmos conflict handling: Define supported multi-region conflict resolution strategy and concurrency controls. What property makes it suitable?
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. It is material here because a multi-write-region Cosmos account can update the same logical item concurrently.
Partition key distribution governs data/throughput placement and query efficiency. Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. It belongs to Azure managed disks. The stated architecture instead relies on: Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. That statement describes Storage service endpoints, while the question asks how Cosmos conflict handling works: Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes.
For the CDN static content requirement, the proposed architecture uses: Use a supported Azure CDN or Front Door static asset distribution approach. Why does that design fit?
Edge content distribution can cache static resources near users. It is material here because marketing assets should be delivered from regional edge nodes instead of a central origin.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. Edge content distribution can cache static resources near users.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. It belongs to Durable Functions orchestration. The stated architecture instead relies on: Edge content distribution can cache static resources near users.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. Edge content distribution can cache static resources near users.
Please check your mailbox for a message from support@examlabs.com and follow the directions.