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 business may lose at most five minutes of writes during failover. An architecture board will approve a solution only if this outcome is demonstrated: Failover comparison shows the latest committed recoverable write is within five minutes. What should be selected?
RPO measures the maximum tolerated data loss period at a recovery point. The selected architecture is use a replication and write-consistency design verified against the five-minute RPO; confirm the result by checking that failover comparison shows the latest committed recoverable write is within five minutes.
Independent crash-consistent snapshots may not preserve database write ordering across disks. The relevant requirement is: A business may lose at most five minutes of writes during failover.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. It does not solve the specified Recovery point objective condition.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. That is useful for Backup private endpoints (Backup workloads in restricted networks must avoid general public service access where supported). It does not meet the current Recovery point objective requirement: A business may lose at most five minutes of writes during failover.
An MSP needs delegated visibility into customer Azure resource monitoring without separate customer logins. A deployment must satisfy this operational criterion: Authorized MSP operators view the delegated customer's resource health from their managing tenant. Which plan is appropriate?
Lighthouse enables delegated management across tenants without relocating customer-owned resources. The selected architecture is use Azure Lighthouse delegated resource management with least-privilege role assignments; confirm the result by checking that authorized MSP operators view the delegated customer's resource health from their managing tenant.
DCRs specify collected streams destinations and transformations for supported agent sources. The current need is: An MSP needs delegated visibility into customer Azure resource monitoring without separate customer logins.
Resource Health reports the platform-side availability history of individual Azure resources. It does not solve the specified Cross-tenant operations condition.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. Its design target is WAF decision logs. The stated requirement instead concerns: An MSP needs delegated visibility into customer Azure resource monitoring without separate customer logins.
Before approving Refactor monolith, the reviewer assesses this requirement: An app must separate independent high-scale workloads and use managed messaging. Which of the reported outcomes is decisive?
Refactoring changes application structure and decouples independent workloads. Confirm using the measurable result: One service can scale independently and failures are isolated through messaging.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. Those observations validate Storage bulk offline transfer. They do not establish the required Refactor monolith result: One service can scale independently and failures are isolated through messaging.
File Sync preserves local namespace access while synchronizing with Azure file shares. The distinguishing check is: 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 Hybrid route validation test checks the Azure workload connects to on-prem data through the approved private network path; the relevant outcome is One service can scale independently and failures are isolated through messaging.
A solution must address both Log anomaly alert and Cross-subscription workspace. First requirement: Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes. Second requirement: Four subscriptions must be searched together during incident response with one KQL query and shared retention policy. Select TWO recommendations that meet these independent needs.
For the Cross-subscription workspace half of this design, a workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. Check: The same query returns events labeled with all four source subscription IDs. The other half concerns Log anomaly alert.
For the Log anomaly alert half of this two-part design, a log search alert can evaluate aggregated matching records instead of only raw metric time series. Verify: A controlled failed-login burst creates the specified log-query alert with source IP context. The other half concerns Cross-subscription workspace.
Analytics and longer-term retention options have different query and storage cost characteristics. Its own validation would be: Recent incidents remain rapidly searchable while older events follow the configured retention policy. The current paired requirement is Log anomaly alert and Cross-subscription workspace.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. The corresponding task is WAF decision logs: The application firewall blocks legitimate requests but developers cannot see the matching rule. It is not one of the two requested controls (Log anomaly alert and Cross-subscription workspace).
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. That plan is appropriate for Azure service health. The two controls sought here are Log anomaly alert and Cross-subscription workspace.
The design team completed work on Resource locks. Its governing requirement was: A business-critical vault should not be deleted during routine administration by contributors. Identify the conclusive verification result.
Locks prevent specified management operations even for users with broad Azure RBAC roles. Confirm using the measurable result: A test deletion is denied while approved read and update actions remain available.
DeployIfNotExists requires remediation for already deployed resources where appropriate. The offered observation would demonstrate Policy remediation: The noncompliant existing resources receive the required settings without manual per-resource editing. The current validation is different: A test deletion is denied while approved read and update actions remain available.
Custom role actions can grant specific management operations without broad Contributor rights. Those observations validate RBAC custom role. They do not establish the required Resource locks result: A test deletion is denied while approved read and update actions remain available.
Policy deny or audit effects can enforce required metadata at supported resource scopes. The distinguishing check is: A test deletion is denied while approved read and update actions remain available.
An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss. Choose the architecture that can be validated by this result: A test failover brings up the application in the recovery region within measured RTO.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. The selected architecture is design Azure Site Recovery replication and recovery plans with test failover; confirm the result by checking that a test failover brings up the application in the recovery region within measured RTO.
Immutable backup settings can prevent specified destructive operations against protected backups. The relevant requirement is: An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss.
Share snapshots preserve file-share point-in-time state for supported restoration. The current need is: An enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. It does not solve the specified Azure Site Recovery failover condition.
The team has justified its Blob ZRS availability design with: Choose zone-redundant storage where the account and service support it. Which statement accurately describes why the approach works?
ZRS synchronously replicates data across primary-region zones. It is material here because a business-critical file repository must survive an availability-zone outage without a regional failover.
Read regions bring replicas closer to users without inherently adding multi-write semantics. ZRS synchronously replicates data across primary-region zones.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. That statement describes Application Gateway zone redundancy, while the question asks how Blob ZRS availability works: ZRS synchronously replicates data across primary-region zones.
Zone-distributed nodes and pod scheduling reduce concentration, but a zone loss can leave pods Pending unless healthy-zone node capacity, quota, volume topology and scheduling constraints permit recovery. ZRS synchronously replicates data across primary-region zones.
Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes. Which Azure architecture would most directly achieve the required result: A controlled failed-login burst creates the specified log-query alert with source IP context?
A log search alert can evaluate aggregated matching records instead of only raw metric time series. The selected architecture is create a scheduled log-search alert that evaluates a KQL query and threshold; confirm the result by checking that 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. It does not solve the specified Log anomaly alert condition.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. Its design target is Web transaction traces. The stated requirement instead concerns: Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The current need is: Security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes.
A service depends on a vendor API password that rotates frequently. Which Azure architecture would most directly achieve the required result: The service uses the new secret version without an embedded password in deployment artifacts?
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The selected architecture is store the password as a versioned Key Vault secret and retrieve it with authorized identity; confirm the result by checking that the service uses the new secret version without an embedded password in deployment artifacts.
Key Vault RBAC data permissions differ from vault resource-management permissions. The relevant requirement is: A service depends on a vendor API password that rotates frequently.
A user-assigned identity has a lifecycle separate from each consuming Azure resource. The current need is: A service depends on a vendor API password that rotates frequently.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. It does not solve the specified Key Vault secrets condition.
Architecture review: Identity-signin monitoring and Control-plane audit. Requirement A: Security analysts require long-term sign-in analysis alongside cloud resource diagnostics. Requirement B: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Which complete two-part proposal satisfies both constraints?
For requirement A, entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. For requirement B, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify both independently: Risky sign-ins can be queried with resource access events over the chosen time window; A denied deployment and a successful resource deletion appear with caller and operation name.
This combines Log anomaly alert and Security-event streaming, which do not satisfy the distinct requirements for Identity-signin monitoring and Control-plane audit.
One action is correct. The other targets Log anomaly alert, leaving Identity-signin monitoring unsolved. Its necessary action is: Export supported Microsoft Entra sign-in logs using diagnostic settings to the approved workspace.
The mismatched half is Security-event streaming; Control-plane audit instead needs: Route Azure Activity Log to a central Log Analytics workspace through diagnostic settings.
Architecture review: Publish subscribe topics and Event Grid notification. Requirement A: Each order event must be processed by billing, shipping and analytics independently. Requirement B: A storage blob upload should notify multiple Azure Functions through filterable event subscriptions. Which complete two-part proposal satisfies both constraints?
For requirement A, topics fan out a message to independently managed subscriptions with durable handling. For requirement B, event Grid distributes discrete source events to configured subscribers. Verify both independently: All three subscribers receive an order event without direct calls from checkout; Only event handlers matching the subject filter are invoked for the test upload.
The option covers one requirement but substitutes Web PubSub real time for Publish subscribe topics. The missing acceptance result is: All three subscribers receive an order event without direct calls from checkout.
Topics fan out a message to independently managed subscriptions with durable handling. Event Grid distributes discrete source events to configured subscribers. The proposed steps (use Azure Web PubSub with authenticated WebSocket clients and appropriate hub design; use Front Door edge caching with appropriate cache-control and purge policy) address other capabilities instead of this required pair.
Topics fan out a message to independently managed subscriptions with durable handling. The other proposed action (use Front Door edge caching with appropriate cache-control and purge policy) addresses a different operation. Event Grid distributes discrete source events to configured subscribers.
Please check your mailbox for a message from support@examlabs.com and follow the directions.