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 VM resource health review proposes: Use Azure Resource Health and resource health alerts for the VM. Which Azure behavior is the technical justification for this decision?
Resource Health reports the platform-side availability history of individual Azure resources. It is material here because a single VM becomes unavailable but the Azure region itself is healthy.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. That statement describes Dynamic baseline alerts, while the question asks how VM resource health works: Resource Health reports the platform-side availability history of individual Azure resources.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. Resource Health reports the platform-side availability history of individual Azure resources.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. It belongs to CPU threshold alerts. The stated architecture instead relies on: Resource Health reports the platform-side availability history of individual Azure resources.
During technical sign-off for Rebuild cloud native, the architect selects: Choose a rebuild approach where business requirements justify new architecture. Which underlying behavior should be documented?
Rebuild replaces the application rather than merely moving its binaries. It is material here because an obsolete application codebase has no maintainable runtime and must use current cloud services.
Offline migration can simplify cutover when application downtime is acceptable. Rebuild replaces the application rather than merely moving its binaries.
Azure Migrate inventories servers and supports readiness and sizing assessments. Rebuild replaces the application rather than merely moving its binaries.
Hybrid reachability depends on both routing and security decisions in the destination VNet. That statement describes Hybrid route validation, while the question asks how Rebuild cloud native works: Rebuild replaces the application rather than merely moving its binaries.
Before approving Blob inventory, the reviewer assesses this requirement: Operations needs a weekly manifest of millions of blobs with properties and access tiers. Which of the reported outcomes is decisive?
Blob Inventory produces scheduled object inventories without crawling each object individually. Confirm using the measurable result: The manifest lists the expected blob properties in the configured destination.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. Those observations validate ADLS ACLs. They do not establish the required Blob inventory result: The manifest lists the expected blob properties in the configured destination.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. The Blob archive rehydration test checks an archived test object is restored to an online tier within the acceptable window; the relevant outcome is The manifest lists the expected blob properties in the configured destination.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The offered observation would demonstrate Azure managed disks: The disk attaches to the VM and meets measured random IO latency. The current validation is different: The manifest lists the expected blob properties in the configured destination.
Architecture rationale review—Policy exemption: Create a scoped policy exemption with justification and expiry rather than deleting the baseline assignment. Which explanation accurately distinguishes this capability?
Policy exemptions record approved exceptions while the policy remains assigned. It is material here because an acquired system has a temporary documented exception to an encryption rule with an expiration date.
Initiatives bundle related policy rules and support shared compliance reporting. It belongs to Policy initiative. The stated architecture instead relies on: Policy exemptions record approved exceptions while the policy remains assigned.
Policy deny or audit effects can enforce required metadata at supported resource scopes. That statement describes Required tag policy, while the question asks how Policy exemption works: Policy exemptions record approved exceptions while the policy remains assigned.
Policy evaluates resource deployment properties and rejects noncompliant regions. Policy exemptions record approved exceptions while the policy remains assigned.
A proposed solution for Azure Batch scheduling is: Use Azure Batch pools, tasks and job orchestration. Select the strongest statement supporting the recommendation.
Azure Batch schedules large-scale parallel workloads across managed compute pools. It is material here because research jobs run thousands of independent parameter simulations and require queued pool-based compute.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. That statement describes Azure HPC design, while the question asks how Azure Batch scheduling works: Azure Batch schedules large-scale parallel workloads across managed compute pools.
Dedicated Host provides physical host isolation with separate placement and pricing controls. Azure Batch schedules large-scale parallel workloads across managed compute pools.
App Service manages web hosting and supports deployment slots on eligible plans. It belongs to App Service web. The stated architecture instead relies on: Azure Batch schedules large-scale parallel workloads across managed compute pools.
The team has justified its App Service isolation design with: Evaluate App Service Environment v3 with supported isolated-tier plans. Which statement accurately describes why the approach works?
ASE provides dedicated App Service hosting in a customer virtual-network environment. It is material here because a regulated web application needs private dedicated hosting and stricter network isolation.
General-purpose VMs balance CPU and memory while retaining OS-level control. ASE provides dedicated App Service hosting in a customer virtual-network environment.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. ASE provides dedicated App Service hosting in a customer virtual-network environment.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. That statement describes Autoscaling based on queue, while the question asks how App Service isolation works: ASE provides dedicated App Service hosting in a customer virtual-network environment.
Architecture rationale review—CPU threshold alerts: Create Azure Monitor metric alert rules with appropriate evaluation windows and an action group. Which explanation accurately distinguishes this capability?
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. It is material here because a fleet needs immediate warning when sustained processor utilization exceeds its target without reading logs manually.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. That statement describes Immutable evidence archive, while the question asks how CPU threshold alerts works: Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query.
VM insights and the agent collect supported guest operating-system counters and process data. Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query.
During technical sign-off for Blob hot/cool/cold, the architect selects: Apply Blob lifecycle management that transitions objects through supported access tiers. Which underlying behavior should be documented?
Tiering trades storage price against access and retrieval cost based on usage. It is material here because a log archive sees frequent access for a month and rare access afterward.
Cosmos DB provides a distributed document database with configurable consistency and throughput. It belongs to Cosmos DB NoSQL. The stated architecture instead relies on: Tiering trades storage price against access and retrieval cost based on usage.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. Tiering trades storage price against access and retrieval cost based on usage.
Blob change feed records changes to blob objects for downstream processing. Tiering trades storage price against access and retrieval cost based on usage.
Architecture review: SQL database monitoring and SQL ledger immutability. Requirement A: DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier. Requirement B: Auditors require cryptographic evidence that transaction history was not tampered with after posting. Which complete two-part proposal satisfies both constraints?
For requirement A, query and resource telemetry helps distinguish costly queries from insufficient database compute. For requirement B, ledger records cryptographically verifiable tamper-evidence for supported relational tables. Verify both independently: Top resource-consuming queries and resource-limit events are visible during peak load; Verification detects an altered historical ledger record during an audit.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The proposed steps (configure SQL dynamic data masking for selected columns and test permission bypass behavior; use SQL system-versioned temporal tables with appropriate retention and permissions) address other capabilities instead of this required pair.
The option covers one requirement but substitutes SQL temporal tables for SQL ledger immutability. The missing acceptance result is: Verification detects an altered historical ledger record during an audit.
One action is correct. The other targets SQL dynamic data masking, leaving SQL database monitoring unsolved. Its necessary action is: Use Azure SQL query performance insight and Azure Monitor metrics/diagnostics.
For the Defender compliance requirement, the proposed architecture uses: Use Microsoft Defender for Cloud regulatory compliance and security posture assessments. Why does that design fit?
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It is material here because security leaders need a consolidated assessment against regulatory cloud control baselines.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Defender for Cloud aggregates recommendations and compliance state for supported frameworks.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. Defender for Cloud aggregates recommendations and compliance state for supported frameworks.
DeployIfNotExists requires remediation for already deployed resources where appropriate. It belongs to Policy remediation. The stated architecture instead relies on: Defender for Cloud aggregates recommendations and compliance state for supported frameworks.
The target environment adopts this approach for Inherited tagging: Use a Policy modify or inherit-tag pattern with appropriate managed identity. What property makes it suitable?
Modify effects can update eligible metadata and require the required remediation permissions. It is material here because projects repeatedly omit the environment tag although the parent resource group has it.
Budgets monitor and notify about spending and do not automatically stop resources. Modify effects can update eligible metadata and require the required remediation permissions.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. It belongs to Management group hierarchy. The stated architecture instead relies on: Modify effects can update eligible metadata and require the required remediation permissions.
Policy deny or audit effects can enforce required metadata at supported resource scopes. That statement describes Required tag policy, while the question asks how Inherited tagging works: Modify effects can update eligible metadata and require the required remediation permissions.
Please check your mailbox for a message from support@examlabs.com and follow the directions.