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 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.
The acceptance criterion for Log anomaly alert comes from this issue: Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes. Which measured outcome is the strongest proof?
A log search alert can evaluate aggregated matching records instead of only raw metric time series. Confirm using the measurable result: A controlled failed-login burst creates the specified log-query alert with source IP context.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. The offered observation would demonstrate CPU threshold alerts: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team. The current validation is different: A controlled failed-login burst creates the specified log-query alert with source IP context.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. Those observations validate Dynamic baseline alerts. They do not establish the required Log anomaly alert result: A controlled failed-login burst creates the specified log-query alert with source IP context.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. The Web transaction traces test checks a failed transaction trace identifies its failing dependency and correlated exception; the relevant outcome is A controlled failed-login burst creates the specified log-query alert with source IP context.
Security operations needs interactive search for 30 days and lower-cost access to older compliance logs. A deployment must satisfy this operational criterion: Recent incidents remain rapidly searchable while older events follow the configured retention policy. Which plan is appropriate?
Analytics and longer-term retention options have different query and storage cost characteristics. The selected architecture is choose appropriate Log Analytics table plans and retention settings for access patterns; confirm the result by checking that recent incidents remain rapidly searchable while older events follow the configured retention policy.
DCRs specify collected streams destinations and transformations for supported agent sources. The current need is: Security operations needs interactive search for 30 days and lower-cost access to older compliance logs.
VM insights and the agent collect supported guest operating-system counters and process data. That is useful for VM guest performance (Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics). It does not meet the current Log retention tiers requirement: Security operations needs interactive search for 30 days and lower-cost access to older compliance logs.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. It does not solve the specified Log retention tiers condition.
Architecture review: Eventual consistency UX and Reliable exactly-once effect. Requirement A: An order service writes asynchronously into a read model and users momentarily see old data. Requirement B: A retrying order processor may receive the same message multiple times and must avoid duplicate billing. Which complete two-part proposal satisfies both constraints?
For requirement A, asynchronous projections can lag writes and need clear read-after-write expectations. For requirement B, at-least-once message delivery requires application logic to deduplicate business side effects. Verify both independently: The UI shows pending status until the read model catches up without duplicate updates; Two deliveries of the same order ID create only one invoice.
Asynchronous projections can lag writes and need clear read-after-write expectations. At-least-once message delivery requires application logic to deduplicate business side effects. The proposed steps (configure API Management rate limiting or quota policies at the appropriate scope; use Front Door edge caching with appropriate cache-control and purge policy) address other capabilities instead of this required pair.
At-least-once message delivery requires application logic to deduplicate business side effects. The other proposed action (configure API Management rate limiting or quota policies at the appropriate scope) does not implement the first control. Asynchronous projections can lag writes and need clear read-after-write expectations.
Asynchronous projections can lag writes and need clear read-after-write expectations. The other proposed action (use Front Door edge caching with appropriate cache-control and purge policy) addresses a different operation. At-least-once message delivery requires application logic to deduplicate business side effects.
A customer-facing API's TLS certificate needs controlled renewal before expiration. Identify the most suitable implementation for an outcome where the renewed certificate is used by the endpoint before the old certificate expires.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. The selected architecture is store and manage the certificate through Key Vault with an approved integration and rotation process; confirm the result by checking that the renewed certificate is used by the endpoint before the old certificate expires.
Secure secret handling removes reusable credentials from source while preserving automation. The relevant requirement is: A customer-facing API's TLS certificate needs controlled renewal before expiration.
Key Vault keys can perform cryptographic operations while restricting private key exposure. The current need is: A customer-facing API's TLS certificate needs controlled renewal before expiration.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. It does not solve the specified Key Vault certificate lifecycle condition.
Operations needs a weekly manifest of millions of blobs with properties and access tiers. An engineer must deliver the following acceptance evidence: The manifest lists the expected blob properties in the configured destination. What design choice is defensible?
Blob Inventory produces scheduled object inventories without crawling each object individually. The selected architecture is configure Azure Storage Blob Inventory reports; confirm the result by checking that the manifest lists the expected blob properties in the configured destination.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. It does not solve the specified Blob inventory condition.
Blob change feed records changes to blob objects for downstream processing. The current need is: Operations needs a weekly manifest of millions of blobs with properties and access tiers.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. That is useful for Blob user-delegation SAS (A partner needs time-limited upload permission to a particular blob without sharing the storage account key). It does not meet the current Blob inventory requirement: Operations needs a weekly manifest of millions of blobs with properties and access tiers.
Before approving Cosmos session consistency, the reviewer assesses this requirement: A customer portal must read its own updates while accepting that other users may briefly see stale writes. Which of the reported outcomes is decisive?
Session consistency offers read-your-writes within a session without strong global consistency. Confirm using the measurable result: The writing session immediately reads its own update while other sessions may lag.
Versioning preserves older object versions independently of current content overwrites. Those observations validate Blob versioning. They do not establish the required Cosmos session consistency result: The writing session immediately reads its own update while other sessions may lag.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The distinguishing check is: The writing session immediately reads its own update while other sessions may lag.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. The offered observation would demonstrate Azure NetApp Files: An authorized NFS client mounts the volume with required throughput. The current validation is different: The writing session immediately reads its own update while other sessions may lag.
The acceptance criterion for Network-flow telemetry comes from this issue: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture. Which measured outcome is the strongest proof?
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. Confirm using the measurable result: A blocked test connection is correlated with its source destination and flow disposition.
Action groups define notifications and automated responses and can be reused by alert rules. The Notification routing test checks a simulated critical alert pages the incident team while a capacity warning sends email only; the relevant outcome is 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. The offered observation would demonstrate Immutable evidence archive: A retained log blob rejects unauthorized deletion during its compliance retention window. The current validation is different: A blocked test connection is correlated with its source destination and flow disposition.
DCRs specify collected streams destinations and transformations for supported agent sources. Those observations validate Agent collection rules. They do not establish the required Network-flow telemetry result: A blocked test connection is correlated with its source destination and flow disposition.
Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics. Choose the architecture that can be validated by this result: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
VM insights and the agent collect supported guest operating-system counters and process data. The selected architecture is enable VM insights with the Azure Monitor Agent and appropriate data collection rule; confirm the result by checking that per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. It does not solve the specified VM guest performance condition.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The current need is: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. That is useful for AKS container diagnosis (An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health). It does not meet the current VM guest performance requirement: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics.
An architect must sign off on SQL customer-managed keys. The business problem is: Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault. What observed test result provides valid evidence?
CMK encryption protects database data at rest while keys are managed under customer control. Confirm using the measurable result: The database reports the approved key as its TDE protector and follows documented key rotation.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Those observations validate SQL ledger immutability. They do not establish the required SQL customer-managed keys result: The database reports the approved key as its TDE protector and follows documented key rotation.
Temporal tables retain row history and support as-of queries independently of whole-database backups. The distinguishing check is: The database reports the approved key as its TDE protector and follows documented key rotation.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. The PostgreSQL flexible server test checks the required extension is available and the app connects without an OS-managed database host; the relevant outcome is The database reports the approved key as its TDE protector and follows documented key rotation.
Before approving Vault network boundary, the reviewer assesses this requirement: A vault must be reachable only from approved private Azure networks and not from arbitrary internet clients. Which of the reported outcomes is decisive?
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. Confirm using the measurable result: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Those observations validate Key Vault secrets. They do not establish the required Vault network boundary result: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Authentication strengths let Conditional Access require supported strong methods based on conditions. The distinguishing check is: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
App-only permissions grant service principal operations without a delegated signed-in user. The Application permissions test checks the service obtains an app-only token and performs only the approved Graph actions; the relevant outcome is A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path.
Please check your mailbox for a message from support@examlabs.com and follow the directions.