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 database-backed application currently stores a SQL password even though it runs on Azure infrastructure. Choose the architecture that can be validated by this result: The workload queries its database with an Entra token and rotation of the former password has no effect.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. The selected architecture is prefer supported Microsoft Entra authentication using the workload managed identity for Azure SQL; confirm the result by checking that the workload queries its database with an Entra token and rotation of the former password has no effect.
PIM can time-bound eligible role activation with approvals MFA and justification. It does not solve the specified Passwordless app connection condition.
Access reviews periodically recertify assigned access and can remove access for denied reviews. Its design target is Identity lifecycle audits. The stated requirement instead concerns: A database-backed application currently stores a SQL password even though it runs on Azure infrastructure.
Key Vault RBAC data permissions differ from vault resource-management permissions. The relevant requirement is: A database-backed application currently stores a SQL password even though it runs on Azure infrastructure.
During technical sign-off for Policy remediation, the architect selects: Create a policy remediation task with suitable identity permissions for supported deployIfNotExists rules. Which underlying behavior should be documented?
DeployIfNotExists requires remediation for already deployed resources where appropriate. It is material here because existing resources are missing diagnostic settings despite new deployments receiving automatic configuration.
Landing zones combine platform foundations with repeatable application subscription governance. That statement describes Landing zones, while the question asks how Policy remediation works: DeployIfNotExists requires remediation for already deployed resources where appropriate.
Policy evaluates resource deployment properties and rejects noncompliant regions. DeployIfNotExists requires remediation for already deployed resources where appropriate.
Modify effects can update eligible metadata and require the required remediation permissions. DeployIfNotExists requires remediation for already deployed resources where appropriate.
To validate the Reliable exactly-once effect deployment, reviewers revisit this operational need: A retrying order processor may receive the same message multiple times and must avoid duplicate billing. What result confirms it was met?
At-least-once message delivery requires application logic to deduplicate business side effects. Confirm using the measurable result: Two deliveries of the same order ID create only one invoice.
APIM can enforce per-client API consumption controls before requests reach backends. The APIM rate limiting test checks a burst beyond the quota is throttled while permitted traffic proceeds; the relevant outcome is Two deliveries of the same order ID create only one invoice.
Edge content distribution can cache static resources near users. The offered observation would demonstrate CDN static content: Measured image latency decreases after the edge cache warms. The current validation is different: Two deliveries of the same order ID create only one invoice.
Failure handling isolates unhealthy dependencies and avoids request pileups. The distinguishing check is: Two deliveries of the same order ID create only one invoice.
Before approving CPU threshold alerts, the reviewer assesses this requirement: A fleet needs immediate warning when sustained processor utilization exceeds its target without reading logs manually. Which of the reported outcomes is decisive?
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. Confirm using the measurable result: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. Those observations validate Immutable evidence archive. They do not establish the required CPU threshold alerts result: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. The distinguishing check is: A simulated sustained high-CPU period fires the metric alert and notifies the on-call team.
VM insights and the agent collect supported guest operating-system counters and process data. The VM guest performance test checks per-VM guest memory and disk metrics appear with host identity in Azure Monitor; the relevant outcome is A simulated sustained high-CPU period fires the metric alert and notifies the on-call team.
The team has justified its Blob change feed design with: Enable the Blob change feed for supported storage accounts. Which statement accurately describes why the approach works?
Blob change feed records changes to blob objects for downstream processing. It is material here because an integration service needs an ordered log of changes to objects without scanning containers every minute.
Versioning preserves older object versions independently of current content overwrites. Blob change feed records changes to blob objects for downstream processing.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. That statement describes Blob object storage, while the question asks how Blob change feed works: Blob change feed records changes to blob objects for downstream processing.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. Blob change feed records changes to blob objects for downstream processing.
Architecture review: Cost export and Cost budgets. Requirement A: Finance must regularly ingest actual cloud cost details into a data warehouse for chargeback. Requirement B: A department must be notified when cloud spend nears its monthly budget without terminating workloads. Which complete two-part proposal satisfies both constraints?
For requirement A, cost exports provide detailed recurring usage data for downstream allocation reporting. For requirement B, budgets monitor and notify about spending and do not automatically stop resources. Verify both independently: A monthly export lands in the correct storage path with resource and cost fields; A threshold crossing issues notifications while the app remains running.
One action is correct. The other targets Role assignment scope, leaving Cost export unsolved. Its necessary action is: Schedule supported Cost Management exports to an authorized storage destination.
Cost exports provide detailed recurring usage data for downstream allocation reporting. Budgets monitor and notify about spending and do not automatically stop resources. The proposed steps (remove broad role inheritance and grant least-scope RBAC at the resource-group boundary; build an Azure Workbook over centrally collected compliance and resource data) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Managed governance dashboards for Cost budgets. The missing acceptance result is: A threshold crossing issues notifications while the app remains running.
The team has justified its Backup vault access design with: Assign scoped backup roles with least privilege and protected operation controls. Which statement accurately describes why the approach works?
Backup-specific RBAC roles separate operational restore tasks from vault administration. It is material here because recovery operators need restore rights but should not be able to delete recovery services resources.
Independent crash-consistent snapshots may not preserve database write ordering across disks. That statement describes Disk snapshot consistency, while the question asks how Backup vault access works: Backup-specific RBAC roles separate operational restore tasks from vault administration.
Immutable backup settings can prevent specified destructive operations against protected backups. Backup-specific RBAC roles separate operational restore tasks from vault administration.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. It belongs to Backup private endpoints. The stated architecture instead relies on: Backup-specific RBAC roles separate operational restore tasks from vault administration.
A solution must address both Required tag policy and Inherited tagging. First requirement: Cost reporting is missing the billing cost center tag on newly created resources. 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 Required tag policy half of this two-part design, policy deny or audit effects can enforce required metadata at supported resource scopes. Verify: An untagged deployment is denied or audited as configured and tagged deployment succeeds. The other half concerns Inherited tagging.
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 Required tag policy.
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. This alternative solves Policy exclusion scope, while the question separately requires Required tag policy and Inherited tagging.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The corresponding task is Defender compliance: Security leaders need a consolidated assessment against regulatory cloud control baselines. It is not one of the two requested controls (Required tag policy and Inherited tagging).
Cost exports provide detailed recurring usage data for downstream allocation reporting. This alternative solves Cost export, while the question separately requires Required tag policy and Inherited tagging.
A production App Service must resist a zone failure without managing VM instances. Identify the most suitable implementation for an outcome where a zonal disruption leaves the application reachable via surviving workers.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. The selected architecture is use a supported zone-redundant App Service plan with adequate instances; confirm the result by checking that a zonal disruption leaves the application reachable via surviving workers.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The current need is: A production App Service must resist a zone failure without managing VM instances.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. It does not solve the specified App Service zone redundancy condition.
Load Balancer routes TCP/UDP flows to healthy backends without terminating HTTP requests. The relevant requirement is: A production App Service must resist a zone failure without managing VM instances.
A rollout addressing Azure Firewall rules has reached acceptance testing. The original problem was: A central security team needs network and application filtering across multiple spokes. Which finding verifies its resolution?
Azure Firewall provides managed stateful filtering with network/application rule models. Confirm using the measurable result: Permitted HTTPS passes inspection while the prohibited destination is blocked.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. The distinguishing check is: Permitted HTTPS passes inspection while the prohibited destination is blocked.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. The Virtual WAN global hubs test checks a branch reaches authorized remote VNets through the intended virtual hub routes; the relevant outcome is Permitted HTTPS passes inspection while the prohibited destination is blocked.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. The offered observation would demonstrate Front Door WAF edge: A permitted request reaches its origin while a malicious test pattern is blocked at the edge. The current validation is different: Permitted HTTPS passes inspection while the prohibited destination is blocked.
Before approving PostgreSQL PITR, the reviewer assesses this requirement: A managed PostgreSQL server is damaged by a schema update and needs its prior state. Which of the reported outcomes is decisive?
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. Confirm using the measurable result: A recovered server answers queries using data from before the accidental update.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. The Blob vaulted backup test checks an eligible blob recovery point is restored using the protected vault workflow; the relevant outcome is A recovered server answers queries using data from before the accidental update.
Backup private connectivity has service and workload prerequisites distinct from ordinary storage private endpoints. Those observations validate Backup private endpoints. They do not establish the required PostgreSQL PITR result: A recovered server answers queries using data from before the accidental update.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. The distinguishing check is: A recovered server answers queries using data from before the accidental update.
Please check your mailbox for a message from support@examlabs.com and follow the directions.