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
To validate the SQL ledger immutability deployment, reviewers revisit this operational need: Auditors require cryptographic evidence that transaction history was not tampered with after posting. What result confirms it was met?
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Confirm using the measurable result: Verification detects an altered historical ledger record during an audit.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Those observations validate SQL connection pooling. They do not establish the required SQL ledger immutability result: Verification detects an altered historical ledger record during an audit.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The distinguishing check is: Verification detects an altered historical ledger record during an audit.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. The SQL schema isolation test checks a tenant restore does not overwrite another tenant's data; the relevant outcome is Verification detects an altered historical ledger record during an audit.
Architecture review: Vault RBAC least privilege and Key Vault cryptographic signing. Requirement A: A team member needs read-only access to selected vault secrets but should not grant access policies. Requirement B: An application must sign payloads with a centrally controlled key without exporting its private material. Which complete two-part proposal satisfies both constraints?
For requirement A, Key Vault RBAC data permissions differ from vault resource-management permissions. For requirement B, Key Vault keys can perform cryptographic operations while restricting private key exposure. Verify both independently: The user retrieves authorized secret values but cannot alter vault access configuration; The application receives a valid signature but cannot export the private key material.
One action is correct. The other targets Azure Files identity access, leaving Vault RBAC least privilege unsolved. Its necessary action is: Assign a suitable Key Vault data-plane RBAC role at a supported minimal scope.
The mismatched half is Managed identity for App Service; Key Vault cryptographic signing instead needs: Use Azure Key Vault key operations with a suitable key type and access permissions.
This combines Azure Files identity access and Managed identity for App Service, which do not satisfy the distinct requirements for Vault RBAC least privilege and Key Vault cryptographic signing.
Architecture review: SQL offline migration and Database schema assessment. Requirement A: A small SQL database can tolerate a planned maintenance outage for cutover. Requirement B: An on-prem SQL app calls deprecated features that Azure SQL Database may not support. Which complete two-part proposal satisfies both constraints?
For requirement A, offline migration can simplify cutover when application downtime is acceptable. For requirement B, target compatibility determines whether code changes or a different managed target are required. Verify both independently: The migrated database passes consistency checks before reopening writes; The assessment reports blocking SQL features and chosen remediation before migration.
This combines Hybrid route validation and Migration landing zone, which do not satisfy the distinct requirements for SQL offline migration and Database schema assessment.
The option covers one requirement but substitutes Migration landing zone for Database schema assessment. The missing acceptance result is: The assessment reports blocking SQL features and chosen remediation before migration.
One action is correct. The other targets Hybrid route validation, leaving SQL offline migration unsolved. Its necessary action is: Use an appropriate offline Azure Database Migration Service path after compatibility review.
A proposed solution for Resource type restriction is: Assign a policy that disallows specified resource types or properties at the unit scope. Select the strongest statement supporting the recommendation.
Azure Policy can deny targeted resource types without revoking all contributor operations. It is material here because a business unit must prevent unapproved public IP resources but permit private network components.
Policy evaluates resource deployment properties and rejects noncompliant regions. Azure Policy can deny targeted resource types without revoking all contributor operations.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Azure Policy can deny targeted resource types without revoking all contributor operations.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. That statement describes Resource group lifecycle, while the question asks how Resource type restriction works: Azure Policy can deny targeted resource types without revoking all contributor operations.
A solution must address both Resource locks and Resource type restriction. First requirement: A business-critical vault should not be deleted during routine administration by contributors. Second requirement: A business unit must prevent unapproved public IP resources but permit private network components. Select TWO recommendations that meet these independent needs.
For the Resource locks half of this two-part design, locks prevent specified management operations even for users with broad Azure RBAC roles. Verify: A test deletion is denied while approved read and update actions remain available. The other half concerns Resource type restriction.
For the Resource type restriction half of this design, Azure Policy can deny targeted resource types without revoking all contributor operations. Check: A public IP create is denied while a private subnet deployment proceeds. The other half concerns Resource locks.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The corresponding task is Role assignment scope: An engineer only operates one network resource group but has Contributor for the whole subscription. It is not one of the two requested controls (Resource locks and Resource type restriction).
Azure service quotas are often scoped by subscription and region and can constrain deployability. Its own validation would be: A capacity forecast and quota decision support the planned deployment without surprise allocation errors. The current paired requirement is Resource locks and Resource type restriction.
Custom role actions can grant specific management operations without broad Contributor rights. The corresponding task is RBAC custom role: A service team needs a narrow set of resource restart and read operations absent from built-in roles. It is not one of the two requested controls (Resource locks and Resource type restriction).
Before approving PostgreSQL read replica, the reviewer assesses this requirement: An application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports. Which of the reported outcomes is decisive?
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. Confirm using the measurable result: The reports run on a replica while primary transaction performance improves.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. The distinguishing check is: The reports run on a replica while primary transaction performance improves.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The offered observation would demonstrate SQL ledger immutability: Verification detects an altered historical ledger record during an audit. The current validation is different: The reports run on a replica while primary transaction performance improves.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Those observations validate PostgreSQL flexible server. They do not establish the required PostgreSQL read replica result: The reports run on a replica while primary transaction performance improves.
Architecture review: Networking cutover DNS and Parallel-run cutover. Requirement A: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint. Requirement B: A financial application requires consistent outputs during migration before stopping the old deployment. Which complete two-part proposal satisfies both constraints?
For requirement A, DNS cutover requires propagation and dependency planning independent of VM replication. For requirement B, parallel operation compares business outputs before committing the cutover. Verify both independently: Clients resolve the new endpoint and the rollback procedure returns traffic if needed; The reconciled reports match while controlled rollback remains available.
The first step implements Retire unused services instead of Networking cutover DNS. The necessary change is to plan DNS TTL reduction, cutover updates and rollback before service migration.
The option covers one requirement but substitutes SQL online migration for Parallel-run cutover. The missing acceptance result is: The reconciled reports match while controlled rollback remains available.
DNS cutover requires propagation and dependency planning independent of VM replication. Parallel operation compares business outputs before committing the cutover. The proposed steps (validate dependencies then retire confirmed redundant workloads from the migration plan; use a supported online migration approach with initial load and continuous changes) address other capabilities instead of this required pair.
Architecture review: Azure Batch scheduling and Azure Functions durable workflow. Requirement A: Research jobs run thousands of independent parameter simulations and require queued pool-based compute. Requirement B: A workflow waits hours between steps while retaining orchestration state through restarts. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure Batch schedules large-scale parallel workloads across managed compute pools. For requirement B, durable Functions manages stateful workflows over serverless function executions. Verify both independently: The submitted job fans out tasks and combines outputs after all simulations complete; A resumed orchestration continues from saved state after a worker restart.
The option covers one requirement but substitutes Dedicated host for Azure Batch scheduling. The missing acceptance result is: The submitted job fans out tasks and combines outputs after all simulations complete.
Azure Batch schedules large-scale parallel workloads across managed compute pools. Durable Functions manages stateful workflows over serverless function executions. The proposed steps (evaluate Azure Dedicated Host with the needed VM families and capacity; select Azure Kubernetes Service with appropriate cluster management guardrails) address other capabilities instead of this required pair.
The mismatched half is AKS full Kubernetes; Azure Functions durable workflow instead needs: Use Durable Functions orchestration with proper idempotent activity design.
The team has justified its SQL compute scaling design with: Plan supported vertical compute scaling and evaluate tier limits and transition impacts. Which statement accurately describes why the approach works?
Managed SQL compute tiers can scale resources but scaling may have operational consequences. It is material here because a database must grow compute during a seasonal sales period but not during idle months.
Read-only replicas can offload reporting from the primary where the tier provides the capability. Managed SQL compute tiers can scale resources but scaling may have operational consequences.
Hyperscale decouples storage scale from compute and supports large database sizes. It belongs to SQL Hyperscale growth. The stated architecture instead relies on: Managed SQL compute tiers can scale resources but scaling may have operational consequences.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. That statement describes SQL database partitioning, while the question asks how SQL compute scaling works: Managed SQL compute tiers can scale resources but scaling may have operational consequences.
For the Retire unused services requirement, the proposed architecture uses: Validate dependencies then retire confirmed redundant workloads from the migration plan. Why does that design fit?
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. It is material here because an application inventory shows unused servers with no business owner or dependent traffic.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. It belongs to Storage bulk offline transfer. The stated architecture instead relies on: Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs.
Refactoring changes application structure and decouples independent workloads. Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs.
PostgreSQL migration requires extension, version and connectivity compatibility checks. Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs.
For the Blob user-delegation SAS requirement, the proposed architecture uses: Issue a scoped user-delegation SAS with the minimum permissions and expiry. Why does that design fit?
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. It is material here because a partner needs time-limited upload permission to a particular blob without sharing the storage account key.
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. That statement describes Storage service endpoints, while the question asks how Blob user-delegation SAS works: A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
Blob Inventory produces scheduled object inventories without crawling each object individually. It belongs to Blob inventory. The stated architecture instead relies on: A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys.
Please check your mailbox for a message from support@examlabs.com and follow the directions.