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 Policy audit versus deny review proposes: Roll out an Azure Policy rule initially with audit then switch to deny after remediation. Which Azure behavior is the technical justification for this decision?
Audit effects collect compliance findings without blocking resource creation. It is material here because the platform team needs to measure the impact of a new restriction before blocking deployments.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. That statement describes Management group hierarchy, while the question asks how Policy audit versus deny works: Audit effects collect compliance findings without blocking resource creation.
Modify effects can update eligible metadata and require the required remediation permissions. Audit effects collect compliance findings without blocking resource creation.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It belongs to Defender compliance. The stated architecture instead relies on: Audit effects collect compliance findings without blocking resource creation.
A file is frequently overwritten and teams need to restore the value before the last upload. Identify the most suitable implementation for an outcome where a previous version can be enumerated and restored after an accidental update.
Versioning preserves older object versions independently of current content overwrites. The selected architecture is enable Blob versioning with retention controls; confirm the result by checking that a previous version can be enumerated and restored after an accidental update.
Bounded staleness constrains replication read lag according to allowed versions/time. It does not solve the specified Blob versioning condition.
Soft delete retains recoverable deleted objects or containers during the configured period. That is useful for Blob soft delete (A developer accidentally deletes a container and the organization wants short-term recovery). It does not meet the current Blob versioning requirement: A file is frequently overwritten and teams need to restore the value before the last upload.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. Its design target is Azure Cache for Redis. The stated requirement instead concerns: A file is frequently overwritten and teams need to restore the value before the last upload.
The design team completed work on Azure Batch scheduling. Its governing requirement was: Research jobs run thousands of independent parameter simulations and require queued pool-based compute. Identify the conclusive verification result.
Azure Batch schedules large-scale parallel workloads across managed compute pools. Confirm using the measurable result: The submitted job fans out tasks and combines outputs after all simulations complete.
Dedicated Host provides physical host isolation with separate placement and pricing controls. Those observations validate Dedicated host. They do not establish the required Azure Batch scheduling result: The submitted job fans out tasks and combines outputs after all simulations complete.
App Service manages web hosting and supports deployment slots on eligible plans. The App Service web test checks traffic swaps to a warmed-up deployment slot without SSH management of app hosts; the relevant outcome is The submitted job fans out tasks and combines outputs after all simulations complete.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. The offered observation would demonstrate Azure HPC design: MPI benchmark meets its target communication latency across allocated nodes. The current validation is different: The submitted job fans out tasks and combines outputs after all simulations complete.
A partner needs time-limited upload permission to a particular blob without sharing the storage account key. A deployment must satisfy this operational criterion: The permitted upload works before expiry while an unauthorized operation and expired token fail. Which plan is appropriate?
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. The selected architecture is issue a scoped user-delegation SAS with the minimum permissions and expiry; confirm the result by checking that the permitted upload works before expiry while an unauthorized operation and expired token fail.
Blob Inventory produces scheduled object inventories without crawling each object individually. It does not solve the specified Blob user-delegation SAS condition.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. The relevant requirement is: A partner needs time-limited upload permission to a particular blob without sharing the storage account key.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. The current need is: A partner needs time-limited upload permission to a particular blob without sharing the storage account key.
An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes. The acceptance test is: Authorized configuration updates succeed but the delete operation is blocked. Which design recommendation best satisfies both?
Management locks guard against accidental resource deletes and operate separately from authorization roles. The selected architecture is add an appropriate CanNotDelete lock while maintaining suitable RBAC permissions; confirm the result by checking that authorized configuration updates succeed but the delete operation is blocked.
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. The relevant requirement is: An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes.
Administrative units scope eligible directory management roles to selected objects, not data visibility. The current need is: An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. It does not solve the specified Resource lock constraints condition.
A proposed solution for Resource locks is: Apply a CanNotDelete resource lock where operational impacts are understood. Select the strongest statement supporting the recommendation.
Locks prevent specified management operations even for users with broad Azure RBAC roles. It is material here because a business-critical vault should not be deleted during routine administration by contributors.
Policy exemptions record approved exceptions while the policy remains assigned. Locks prevent specified management operations even for users with broad Azure RBAC roles.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Locks prevent specified management operations even for users with broad Azure RBAC roles.
Azure deployment what-if previews resource changes before applying a template. It belongs to Deployment drift. The stated architecture instead relies on: Locks prevent specified management operations even for users with broad Azure RBAC roles.
A proposed solution for SQL Always Encrypted is: Use SQL Always Encrypted with appropriate key management and compatible client drivers. Select the strongest statement supporting the recommendation.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. It is material here because a database handles patient identifiers that should stay encrypted from database administrators during normal access.
SQL auditing captures database events as configured separately from application request telemetry. Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine.
Elastic pools share resources across independent databases with non-synchronized demand. That statement describes SQL elastic pool, while the question asks how SQL Always Encrypted works: Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine.
Architecture review: ExpressRoute private circuit and Point-to-site VPN. Requirement A: A large enterprise needs private reliable WAN connectivity to Azure at scale. Requirement B: Remote administrators need individually authenticated encrypted connectivity to Azure private resources. Which complete two-part proposal satisfies both constraints?
For requirement A, expressRoute links customer WAN to Azure backbone privately through provider connectivity. For requirement B, point-to-site VPN authenticates individual clients for private network access. Verify both independently: A test workload reaches Azure over advertised private prefixes when one circuit path fails; Authorized clients connect privately and revoked clients cannot establish a tunnel.
The mismatched half is Front Door WAF edge; Point-to-site VPN instead needs: Use Azure VPN Gateway point-to-site with an appropriate identity provider.
The first step implements NAT Gateway outbound instead of ExpressRoute private circuit. The necessary change is to use ExpressRoute private peering with redundant circuit/provider design.
Both proposed halves address other use cases: NAT Gateway outbound and Front Door WAF edge. The requested pair is ExpressRoute private circuit and Point-to-site VPN.
Architecture review: Cross-subscription workspace and Database resource diagnostics. Requirement A: Four subscriptions must be searched together during incident response with one KQL query and shared retention policy. Requirement B: A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records. Which complete two-part proposal satisfies both constraints?
For requirement A, a workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. For requirement B, resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. Verify both independently: The same query returns events labeled with all four source subscription IDs; SQL diagnostic records appear in the target workspace and can be filtered by database name.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The proposed steps (export supported Microsoft Entra sign-in logs using diagnostic settings to the approved workspace; use Kusto Query Language against the instrumented telemetry workspace) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Error trend queries for Database resource diagnostics. The missing acceptance result is: SQL diagnostic records appear in the target workspace and can be filtered by database name.
One action is correct. The other targets Identity-signin monitoring, leaving Cross-subscription workspace unsolved. Its necessary action is: Send supported resource logs from each subscription into a centralized Log Analytics workspace.
An architect must sign off on Allowed regions. The business problem is: Data sovereignty policy forbids new resources outside a small list of approved Azure regions. What observed test result provides valid evidence?
Policy evaluates resource deployment properties and rejects noncompliant regions. Confirm using the measurable result: A forbidden-region deployment is denied and an allowed-region deployment succeeds.
Custom role actions can grant specific management operations without broad Contributor rights. The offered observation would demonstrate RBAC custom role: The operator restarts an approved service and cannot modify resource access assignments. The current validation is different: A forbidden-region deployment is denied and an allowed-region deployment succeeds.
Infrastructure as code declares desired resources and allows review and repeat deployment. The distinguishing check is: A forbidden-region deployment is denied and an allowed-region deployment succeeds.
Azure service quotas are often scoped by subscription and region and can constrain deployability. The Quotas and limits test checks a capacity forecast and quota decision support the planned deployment without surprise allocation errors; the relevant outcome is A forbidden-region deployment is denied and an allowed-region deployment succeeds.
Architecture review: CPU threshold alerts and Dynamic baseline alerts. Requirement A: A fleet needs immediate warning when sustained processor utilization exceeds its target without reading logs manually. Requirement B: A seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue. Which complete two-part proposal satisfies both constraints?
For requirement A, metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. For requirement B, dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. Verify both independently: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team; The routine daily spike is tolerated while an atypical surge creates an actionable alert.
The option covers one requirement but substitutes Cross-tenant operations for Dynamic baseline alerts. The missing acceptance result is: The routine daily spike is tolerated while an atypical surge creates an actionable alert.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The other proposed action (enable Azure Monitor managed service for Prometheus for supported Kubernetes clusters) does not implement the first control. Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query.
This combines Managed Prometheus and Cross-tenant operations, which do not satisfy the distinct requirements for CPU threshold alerts and Dynamic baseline alerts.
Please check your mailbox for a message from support@examlabs.com and follow the directions.