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
An architect must sign off on VM resource health. The business problem is: A single VM becomes unavailable but the Azure region itself is healthy. What observed test result provides valid evidence?
Resource Health reports the platform-side availability history of individual Azure resources. Confirm using the measurable result: The specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The Dynamic baseline alerts test checks the routine daily spike is tolerated while an atypical surge creates an actionable alert; the relevant outcome is The specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The offered observation would demonstrate Database resource diagnostics: SQL diagnostic records appear in the target workspace and can be filtered by database name. The current validation is different: The specific VM shows an unavailable health state while the regional Service Health feed remains normal.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. The distinguishing check is: The specific VM shows an unavailable health state while the regional Service Health feed remains normal.
A solution must address both Service Bus ordering and Stream Analytics window. First requirement: A billing workflow needs durable work messages with transactions, sessions and dead-letter handling. Second requirement: A telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code. Select TWO recommendations that meet these independent needs.
For the Service Bus ordering half of this two-part design, service Bus is an enterprise message broker with delivery and dead-letter semantics. Verify: A poison message moves to the dead-letter queue while ordered session items retain their sequence. The other half concerns Stream Analytics window.
For the Stream Analytics window half of this design, stream Analytics supports SQL-like processing over streaming sources with time windows. Check: An expected count is emitted for each completed five-minute event window. The other half concerns Service Bus ordering.
Mapping data flows transform data on managed Spark compute from graphical mappings. The corresponding task is ADF mapping data flow: An analyst wants a GUI-defined transformation over millions of input rows without maintaining Spark scripts. It is not one of the two requested controls (Service Bus ordering and Stream Analytics window).
Tumbling-window triggers model contiguous time slices with support for backfill. Its own validation would be: A missed hour is scheduled for a controlled rerun rather than silently skipped. The current paired requirement is Service Bus ordering and Stream Analytics window.
A stored watermark limits reads to changes after the last successful processed interval. This alternative solves ADF incremental copy, while the question separately requires Service Bus ordering and Stream Analytics window.
A solution must address both Standardized IaC and Required tag policy. First requirement: Operations wants reproducible Azure environment deployments from version-controlled definitions. Second requirement: Cost reporting is missing the billing cost center tag on newly created resources. Select TWO recommendations that meet these independent needs.
For the Standardized IaC half of this two-part design, infrastructure as code declares desired resources and allows review and repeat deployment. Verify: The same versioned module deploys matching compliant resources across test environments. The other half concerns Required tag policy.
For the Required tag policy half of this design, policy deny or audit effects can enforce required metadata at supported resource scopes. Check: An untagged deployment is denied or audited as configured and tagged deployment succeeds. The other half concerns Standardized IaC.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The corresponding task is Defender compliance: Security leaders need a consolidated assessment against regulatory cloud control baselines. It is not one of the two requested controls (Standardized IaC and Required tag policy).
Locks prevent specified management operations even for users with broad Azure RBAC roles. This alternative solves Resource locks, while the question separately requires Standardized IaC and Required tag policy.
Policy exemptions record approved exceptions while the policy remains assigned. The corresponding task is Policy exemption: An acquired system has a temporary documented exception to an encryption rule with an expiration date. It is not one of the two requested controls (Standardized IaC and Required tag policy).
Operations must aggregate intermittent HTTP 500s by service and hour from application traces. An architecture board will approve a solution only if this outcome is demonstrated: An hourly chart returns grouped failure counts and identifies the affected service. What should be selected?
KQL summarizes timestamped structured log data across dimensions such as operation and cloud role. The selected architecture is use Kusto Query Language against the instrumented telemetry workspace; confirm the result by checking that an hourly chart returns grouped failure counts and identifies the affected service.
Resource Health reports the platform-side availability history of individual Azure resources. Its design target is VM resource health. The stated requirement instead concerns: Operations must aggregate intermittent HTTP 500s by service and hour from application traces.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. The relevant requirement is: Operations must aggregate intermittent HTTP 500s by service and hour from application traces.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. It does not solve the specified Error trend queries condition.
For the Front Door global failover requirement, the proposed architecture uses: Use Azure Front Door with origins and origin health probes. Why does that design fit?
Front Door provides global application delivery and HTTP(S) origin failover at the edge. It is material here because two regional web endpoints need internet-edge routing and automatic failover to a healthy region.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. That statement describes AKS cluster autoscaler, while the question asks how Front Door global failover works: Front Door provides global application delivery and HTTP(S) origin failover at the edge.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Front Door provides global application delivery and HTTP(S) origin failover at the edge.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. It belongs to Circuit breaker behavior. The stated architecture instead relies on: Front Door provides global application delivery and HTTP(S) origin failover at the edge.
The target environment adopts this approach for Control-plane audit: Route Azure Activity Log to a central Log Analytics workspace through diagnostic settings. What property makes it suitable?
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. It is material here because a tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The Activity Log records Azure Resource Manager control-plane events independent of guest agents.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. The Activity Log records Azure Resource Manager control-plane events independent of guest agents.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. It belongs to Automated diagnostics policy. The stated architecture instead relies on: The Activity Log records Azure Resource Manager control-plane events independent of guest agents.
The Key Vault certificate lifecycle review proposes: Store and manage the certificate through Key Vault with an approved integration and rotation process. Which Azure behavior is the technical justification for this decision?
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. It is material here because 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 belongs to Vault network boundary. The stated architecture instead relies on: Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations.
Key Vault keys can perform cryptographic operations while restricting private key exposure. That statement describes Key Vault cryptographic signing, while the question asks how Key Vault certificate lifecycle works: Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations.
Secure secret handling removes reusable credentials from source while preserving automation. Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations.
Architecture review: Storage bulk offline transfer and VM agentless migration. Requirement A: A remote facility must move 500 TB to Azure but WAN bandwidth is too slow for the deadline. Requirement B: VMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign. Which complete two-part proposal satisfies both constraints?
For requirement A, physical data transfer can shorten initial bulk migration when network transfer is impractical. For requirement B, server migration replication supports lift-and-shift of eligible VM workloads to Azure. Verify both independently: The imported objects reconcile against checksums and manifests; A test migration boots the replicated VM and validates application dependencies.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Server migration replication supports lift-and-shift of eligible VM workloads to Azure. The proposed steps (create an Azure landing zone before migration waves using CAF guidance; use a supported online migration approach with initial load and continuous changes) address other capabilities instead of this required pair.
The mismatched half is SQL online migration; VM agentless migration instead needs: Use an appropriate Azure Migrate server migration path after appliance assessment.
The option covers one requirement but substitutes Migration landing zone for Storage bulk offline transfer. The missing acceptance result is: The imported objects reconcile against checksums and manifests.
Before approving Zone-redundant load balancer, the reviewer assesses this requirement: A regional application needs one L4 frontend distributing traffic to healthy VMs across zones. Which of the reported outcomes is decisive?
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. Confirm using the measurable result: Failed backend probes remove one instance and healthy zonal instances continue serving.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The offered observation would demonstrate Circuit breaker behavior: Unhealthy requests fail quickly and the service resumes calls after recovery. The current validation is different: Failed backend probes remove one instance and healthy zonal instances continue serving.
Failover-group listeners abstract the primary location during regional failover. Those observations validate SQL failover groups HA. They do not establish the required Zone-redundant load balancer result: Failed backend probes remove one instance and healthy zonal instances continue serving.
Read regions bring replicas closer to users without inherently adding multi-write semantics. The distinguishing check is: Failed backend probes remove one instance and healthy zonal instances continue serving.
The target environment adopts this approach for PIM on-demand roles: Configure Privileged Identity Management for Azure resource roles with activation controls. What property makes it suitable?
PIM can time-bound eligible role activation with approvals MFA and justification. It is material here because 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. PIM can time-bound eligible role activation with approvals MFA and justification.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. PIM can time-bound eligible role activation with approvals MFA and justification.
App-only permissions grant service principal operations without a delegated signed-in user. It belongs to Application permissions. The stated architecture instead relies on: PIM can time-bound eligible role activation with approvals MFA and justification.
A developer accidentally deletes a container and the organization wants short-term recovery. The acceptance test is: An accidentally deleted test object is recovered before retention expires. Which design recommendation best satisfies both?
Soft delete retains recoverable deleted objects or containers during the configured period. The selected architecture is enable appropriate Blob and container soft-delete features within retention; confirm the result by checking that an accidentally deleted test object is recovered before retention expires.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. It does not solve the specified Blob soft delete condition.
Versioning preserves older object versions independently of current content overwrites. That is useful for Blob versioning (A file is frequently overwritten and teams need to restore the value before the last upload). It does not meet the current Blob soft delete requirement: A developer accidentally deletes a container and the organization wants short-term recovery.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. The relevant requirement is: A developer accidentally deletes a container and the organization wants short-term recovery.
Please check your mailbox for a message from support@examlabs.com and follow the directions.