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 rollout addressing Managed governance dashboards has reached acceptance testing. The original problem was: Auditors need repeatable visual reporting of compliance violations across many subscriptions. Which finding verifies its resolution?
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. Confirm using the measurable result: An auditor filters noncompliant resources by subscription and policy assignment.
Budgets monitor and notify about spending and do not automatically stop resources. The offered observation would demonstrate Cost budgets: A threshold crossing issues notifications while the app remains running. The current validation is different: An auditor filters noncompliant resources by subscription and policy assignment.
Initiatives bundle related policy rules and support shared compliance reporting. Those observations validate Policy initiative. They do not establish the required Managed governance dashboards result: An auditor filters noncompliant resources by subscription and policy assignment.
Landing zones combine platform foundations with repeatable application subscription governance. The distinguishing check is: An auditor filters noncompliant resources by subscription and policy assignment.
The target environment adopts this approach for VNet peering: Use VNet peering or global VNet peering under the supported region topology. What property makes it suitable?
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. It is material here because two Azure VNets in nearby regions need low-latency private connectivity without VPN gateways.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. It belongs to Application Gateway internal. The stated architecture instead relies on: Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default.
A proposed subscription hosts many public IPs and compute cores beyond regional quota. An engineer must deliver the following acceptance evidence: A capacity forecast and quota decision support the planned deployment without surprise allocation errors. What design choice is defensible?
Azure service quotas are often scoped by subscription and region and can constrain deployability. The selected architecture is check subscription and regional service quotas before architecture signoff and request increases; confirm the result by checking that a capacity forecast and quota decision support the planned deployment without surprise allocation errors.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. That is useful for Managed governance dashboards (Auditors need repeatable visual reporting of compliance violations across many subscriptions). It does not meet the current Quotas and limits requirement: A proposed subscription hosts many public IPs and compute cores beyond regional quota.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Its design target is Defender compliance. The stated requirement instead concerns: A proposed subscription hosts many public IPs and compute cores beyond regional quota.
Locks prevent specified management operations even for users with broad Azure RBAC roles. It does not solve the specified Quotas and limits condition.
The acceptance criterion for SQL long-term recovery comes from this issue: A legal obligation requires recovery of relational records from a backup taken five years ago. Which measured outcome is the strongest proof?
LTR retains selected full backups over years rather than only the standard short PITR window. Confirm using the measurable result: A designated five-year backup remains listed and can restore a compliant copy.
Immutable backup settings can prevent specified destructive operations against protected backups. The distinguishing check is: A designated five-year backup remains listed and can restore a compliant copy.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The SQL geo-restore test checks a region-loss exercise recovers a database from the latest supported geo backup; the relevant outcome is A designated five-year backup remains listed and can restore a compliant copy.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. The offered observation would demonstrate Cross-region backup: A supported secondary-region restore yields the expected recovery point. The current validation is different: A designated five-year backup remains listed and can restore a compliant copy.
Architecture rationale review—Agent collection rules: Use Azure Monitor Agent data collection rules targeted through data collection rule associations. Which explanation accurately distinguishes this capability?
DCRs specify collected streams destinations and transformations for supported agent sources. It is material here because windows servers send performance counters that should differ by workload and environment.
Analytics and longer-term retention options have different query and storage cost characteristics. That statement describes Log retention tiers, while the question asks how Agent collection rules works: DCRs specify collected streams destinations and transformations for supported agent sources.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. DCRs specify collected streams destinations and transformations for supported agent sources.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. It belongs to Immutable evidence archive. The stated architecture instead relies on: DCRs specify collected streams destinations and transformations for supported agent sources.
A Cosmos DB workload uses periodic backups and the team expects minute-level arbitrary restores. A deployment must satisfy this operational criterion: The new design demonstrates recovery granularity consistent with the RPO. Which plan is appropriate?
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. The selected architecture is evaluate continuous-backup mode if precise PITR is a firm requirement; confirm the result by checking that the new design demonstrates recovery granularity consistent with the RPO.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The relevant requirement is: A Cosmos DB workload uses periodic backups and the team expects minute-level arbitrary restores.
Immutable backup settings can prevent specified destructive operations against protected backups. It does not solve the specified Cosmos periodic backup condition.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Its design target is Blob vaulted backup. The stated requirement instead concerns: A Cosmos DB workload uses periodic backups and the team expects minute-level arbitrary restores.
To validate the DDoS protection deployment, reviewers revisit this operational need: A publicly reachable application needs additional DDoS mitigation beyond basic platform protections. What result confirms it was met?
DDoS protection adds adaptive mitigation and telemetry for supported public resources. Confirm using the measurable result: Protection coverage reports the eligible public IP and test telemetry is available.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. Those observations validate Application Gateway internal. They do not establish the required DDoS protection result: Protection coverage reports the eligible public IP and test telemetry is available.
VPN Gateway can establish encrypted IPsec tunnels over public networks. The distinguishing check is: Protection coverage reports the eligible public IP and test telemetry is available.
VNet integration is principally an outbound feature; inbound private access requires other controls. The VNet integration App Service test checks the app connects to private SQL via VNet while its public frontend remains reachable as intended; the relevant outcome is Protection coverage reports the eligible public IP and test telemetry is available.
A solution must address both Role assignment scope and Inherited tagging. First requirement: An engineer only operates one network resource group but has Contributor for the whole subscription. Second requirement: Projects repeatedly omit the environment tag although the parent resource group has it. Select TWO recommendations that meet these independent needs.
For the Inherited tagging half of this design, modify effects can update eligible metadata and require the required remediation permissions. Check: New supported resources inherit the resource-group environment tag after assignment. The other half concerns Role assignment scope.
For the Role assignment scope half of this two-part design, RBAC assignments inherit downward so narrower scope reduces unintended changes. Verify: The engineer can change the assigned network group but not another group's resources. The other half concerns Inherited tagging.
Azure Policy can deny targeted resource types without revoking all contributor operations. That plan is appropriate for Resource type restriction. The two controls sought here are Role assignment scope and Inherited tagging.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. Its own validation would be: Deleting an approved test resource group removes only the intended environment resources. The current paired requirement is Role assignment scope and Inherited tagging.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. The corresponding task is Management group hierarchy: A global enterprise requires central baseline policies applied to every subscription but autonomous project teams manage resources. It is not one of the two requested controls (Role assignment scope and Inherited tagging).
Before approving Managed identity for App Service, the reviewer assesses this requirement: A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings. Which of the reported outcomes is decisive?
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. Confirm using the measurable result: A token-based read works and the app has no stored storage-account key.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. The Consumer sign-in test checks the consumer completes the intended registration journey without receiving workforce resource roles; the relevant outcome is A token-based read works and the app has no stored storage-account key.
Key Vault keys can perform cryptographic operations while restricting private key exposure. The offered observation would demonstrate Key Vault cryptographic signing: The application receives a valid signature but cannot export the private key material. The current validation is different: A token-based read works and the app has no stored storage-account key.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. The distinguishing check is: A token-based read works and the app has no stored storage-account key.
A proposed solution for Application Gateway internal is: Use Application Gateway with an internal frontend IP and suitable WAF tier. Select the strongest statement supporting the recommendation.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. It is material here because an internal web app needs URL path routing and WAF-like inspection behind a private frontend.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. Application Gateway provides regional Layer 7 reverse proxy and routing for private backends.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Application Gateway provides regional Layer 7 reverse proxy and routing for private backends.
Private DNS zone links determine name resolution for VNets that consume private endpoints. It belongs to DNS private zones. The stated architecture instead relies on: Application Gateway provides regional Layer 7 reverse proxy and routing for private backends.
The acceptance criterion for Azure Data Explorer telemetry comes from this issue: A security team needs interactive time-series queries across petabytes of ingested machine events. Which measured outcome is the strongest proof?
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. Confirm using the measurable result: A filtered time-series KQL query returns the needed event trend within response goals.
Mapping data flows transform data on managed Spark compute from graphical mappings. The distinguishing check is: A filtered time-series KQL query returns the needed event trend within response goals.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. The Service Bus ordering test checks a poison message moves to the dead-letter queue while ordered session items retain their sequence; the relevant outcome is A filtered time-series KQL query returns the needed event trend within response goals.
Stream Analytics supports SQL-like processing over streaming sources with time windows. The offered observation would demonstrate Stream Analytics window: An expected count is emitted for each completed five-minute event window. The current validation is different: A filtered time-series KQL query returns the needed event trend within response goals.
Please check your mailbox for a message from support@examlabs.com and follow the directions.