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
During technical sign-off for Managed governance dashboards, the architect selects: Build an Azure Workbook over centrally collected compliance and resource data. Which underlying behavior should be documented?
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. It is material here because auditors need repeatable visual reporting of compliance violations across many subscriptions.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
DeployIfNotExists requires remediation for already deployed resources where appropriate. Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It belongs to Defender compliance. The stated architecture instead relies on: Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself.
A rollout addressing Vault RBAC least privilege has reached acceptance testing. The original problem was: A team member needs read-only access to selected vault secrets but should not grant access policies. Which finding verifies its resolution?
Key Vault RBAC data permissions differ from vault resource-management permissions. Confirm using the measurable result: The user retrieves authorized secret values but cannot alter vault access configuration.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. The offered observation would demonstrate Vault network boundary: A workload resolves the private vault endpoint and a public-network test cannot use the forbidden path. The current validation is different: The user retrieves authorized secret values but cannot alter vault access configuration.
Access reviews periodically recertify assigned access and can remove access for denied reviews. The distinguishing check is: The user retrieves authorized secret values but cannot alter vault access configuration.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The Resource lock constraints test checks authorized configuration updates succeed but the delete operation is blocked; the relevant outcome is The user retrieves authorized secret values but cannot alter vault access configuration.
An app must separate independent high-scale workloads and use managed messaging. An engineer must deliver the following acceptance evidence: One service can scale independently and failures are isolated through messaging. What design choice is defensible?
Refactoring changes application structure and decouples independent workloads. The selected architecture is plan an incremental refactor into bounded services with asynchronous integration; confirm the result by checking that one service can scale independently and failures are isolated through messaging.
Hybrid reachability depends on both routing and security decisions in the destination VNet. The current need is: An app must separate independent high-scale workloads and use managed messaging.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Its design target is Storage bulk offline transfer. The stated requirement instead concerns: An app must separate independent high-scale workloads and use managed messaging.
File Sync preserves local namespace access while synchronizing with Azure file shares. It does not solve the specified Refactor monolith condition.
Auditors require cryptographic evidence that transaction history was not tampered with after posting. The acceptance test is: Verification detects an altered historical ledger record during an audit. Which design recommendation best satisfies both?
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The selected architecture is evaluate Azure SQL ledger tables with verifiable database digests; confirm the result by checking that verification detects an altered historical ledger record during an audit.
Flexible Server provides managed MySQL compute storage and backups. Its design target is MySQL managed service. The stated requirement instead concerns: Auditors require cryptographic evidence that transaction history was not tampered with after posting.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. The relevant requirement is: Auditors require cryptographic evidence that transaction history was not tampered with after posting.
Read-only replicas can offload reporting from the primary where the tier provides the capability. It does not solve the specified SQL ledger immutability condition.
For the Blob operational backup requirement, the proposed architecture uses: Use supported blob operational backup with versioning and change feed prerequisites. Why does that design fit?
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. It is material here because blob containers need protection against accidental deletion and malicious modification over a short operational window.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. Blob operational backup relies on point-in-time object protection features rather than VM-level backups.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. Blob operational backup relies on point-in-time object protection features rather than VM-level backups.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. It belongs to SQL database PITR. The stated architecture instead relies on: Blob operational backup relies on point-in-time object protection features rather than VM-level backups.
The design team completed work on VM guest performance. Its governing requirement was: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics. Identify the conclusive verification result.
VM insights and the agent collect supported guest operating-system counters and process data. Confirm using the measurable result: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. Those observations validate Security-event streaming. They do not establish the required VM guest performance result: 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. The distinguishing check is: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. The AKS container diagnosis test checks the restarting pod and its container events are visible with node and namespace context; the relevant outcome is Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
A proposed solution for Multifactor critical operations is: Use Azure Backup multi-user authorization with resource guard for protected operations. Select the strongest statement supporting the recommendation.
Multi-user authorization separates approval boundaries for critical backup changes. It is material here because ransomware attackers should not disable backup protection with a single compromised admin account.
Nightly backups alone do not provide continuous workload replication or low recovery time. It belongs to Backup versus DR. The stated architecture instead relies on: Multi-user authorization separates approval boundaries for critical backup changes.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. That statement describes Recovery drill governance, while the question asks how Multifactor critical operations works: Multi-user authorization separates approval boundaries for critical backup changes.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. Multi-user authorization separates approval boundaries for critical backup changes.
Architecture review: Blob GZRS durability and Blob ZRS availability. Requirement A: A critical object store needs zone resilience in primary and a regional recovery copy. Requirement B: A business-critical file repository must survive an availability-zone outage without a regional failover. Which complete two-part proposal satisfies both constraints?
For requirement A, GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. For requirement B, ZRS synchronously replicates data across primary-region zones. Verify both independently: A regional recovery plan uses the secondary while zonal faults leave primary available; Reading and writing a test blob continues while one zone is unavailable.
ZRS synchronously replicates data across primary-region zones. The other proposed action (use zone-aware node pools and workload spread/anti-affinity policies) does not implement the first control. GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region.
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. The other proposed action (use Virtual Machine Scale Sets with autoscale rules and a stateless design) addresses a different operation. ZRS synchronously replicates data across primary-region zones.
Both proposed halves address other use cases: AKS availability zones and VM scale set autoscaling. The requested pair is Blob GZRS durability and Blob ZRS availability.
The design team completed work on Azure Site Recovery failover. Its governing requirement was: An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss. Identify the conclusive verification result.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. Confirm using the measurable result: A test failover brings up the application in the recovery region within measured RTO.
LTR retains selected full backups over years rather than only the standard short PITR window. The SQL long-term recovery test checks a designated five-year backup remains listed and can restore a compliant copy; the relevant outcome is A test failover brings up the application in the recovery region within measured RTO.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The offered observation would demonstrate Blob vaulted backup: An eligible blob recovery point is restored using the protected vault workflow. The current validation is different: A test failover brings up the application in the recovery region within measured RTO.
Backup-specific RBAC roles separate operational restore tasks from vault administration. Those observations validate Backup vault access. They do not establish the required Azure Site Recovery failover result: A test failover brings up the application in the recovery region within measured RTO.
A nightly ingestion job must process every hourly window and backfill missed intervals after outages. Identify the most suitable implementation for an outcome where a missed hour is scheduled for a controlled rerun rather than silently skipped.
Tumbling-window triggers model contiguous time slices with support for backfill. The selected architecture is use Data Factory tumbling-window triggers with dependency and retry design; confirm the result by checking that a missed hour is scheduled for a controlled rerun rather than silently skipped.
A stored watermark limits reads to changes after the last successful processed interval. It does not solve the specified ADF tumbling window condition.
Self-hosted integration runtime initiates supported outbound communications to access private sources. That is useful for Data Factory hybrid copy (A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port). It does not meet the current ADF tumbling window requirement: A nightly ingestion job must process every hourly window and backfill missed intervals after outages.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Its design target is Synapse dedicated SQL. The stated requirement instead concerns: A nightly ingestion job must process every hourly window and backfill missed intervals after outages.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.