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
For the SQL dynamic data masking requirement, the proposed architecture uses: Configure SQL dynamic data masking for selected columns and test permission bypass behavior. Why does that design fit?
Dynamic data masking limits exposure in query results but is not a substitute for database access control. It is material here because customer support may query a user table but should not see complete personal identifiers in routine result sets.
Pooling reuses connections and reduces setup overhead relative to per-request creation. Dynamic data masking limits exposure in query results but is not a substitute for database access control.
Migration assessment identifies blockers and target-fit issues before a cutover. That statement describes SQL migration assessment, while the question asks how SQL dynamic data masking works: Dynamic data masking limits exposure in query results but is not a substitute for database access control.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Dynamic data masking limits exposure in query results but is not a substitute for database access control.
The target environment adopts this approach for Graceful scale-in: Implement connection draining, termination grace periods and readiness controls as supported. What property makes it suitable?
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. It is material here because a stateless API behind a load balancer loses in-flight requests when autoscale removes instances mid-response.
A zone-separated standby supports automated failover where offered. It belongs to PostgreSQL zone redundant HA. The stated architecture instead relies on: Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. That statement describes Front Door global failover, while the question asks how Graceful scale-in works: Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic.
Zone redundancy spreads eligible database availability replicas across zones. Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic.
During technical sign-off for SQL auditing, the architect selects: Enable Azure SQL auditing to an approved storage or monitoring destination. Which underlying behavior should be documented?
SQL auditing captures database events as configured separately from application request telemetry. It is material here because compliance requires records of login attempts and selected database actions independent of app logs.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. That statement describes SQL dynamic data masking, while the question asks how SQL auditing works: SQL auditing captures database events as configured separately from application request telemetry.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. SQL auditing captures database events as configured separately from application request telemetry.
Hyperscale decouples storage scale from compute and supports large database sizes. It belongs to SQL Hyperscale growth. The stated architecture instead relies on: SQL auditing captures database events as configured separately from application request telemetry.
The acceptance criterion for Cosmos partition key comes from this issue: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling. Which measured outcome is the strongest proof?
Partition key distribution governs data/throughput placement and query efficiency. Confirm using the measurable result: RU consumption distributes across partitions and the query includes its expected partition key.
Blob Inventory produces scheduled object inventories without crawling each object individually. The offered observation would demonstrate Blob inventory: The manifest lists the expected blob properties in the configured destination. The current validation is different: RU consumption distributes across partitions and the query includes its expected partition key.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. Those observations validate Premium SSD v2. They do not establish the required Cosmos partition key result: RU consumption distributes across partitions and the query includes its expected partition key.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. The Cosmos conflict handling test checks a controlled simultaneous update resolves according to the documented business rule; the relevant outcome is RU consumption distributes across partitions and the query includes its expected partition key.
The team has justified its Compute optimized VM design with: Choose a compute-optimized VM family sized for sustained CPU throughput. Which statement accurately describes why the approach works?
Compute-optimized instances prioritize vCPU capacity over excess memory. It is material here because a stateless batch worker is CPU-bound with little disk IO or memory pressure.
Azure Batch schedules large-scale parallel workloads across managed compute pools. It belongs to Azure Batch scheduling. The stated architecture instead relies on: Compute-optimized instances prioritize vCPU capacity over excess memory.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. That statement describes Memory optimized VM, while the question asks how Compute optimized VM works: Compute-optimized instances prioritize vCPU capacity over excess memory.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. Compute-optimized instances prioritize vCPU capacity over excess memory.
Architecture rationale review—UDR firewall inspection: Configure a route table with default route next hop to the firewall and enable required forwarding. Which explanation accurately distinguishes this capability?
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. It is material here because a subnet must send internet-bound flows through a centrally managed inspection firewall.
VNet peering alone is not transitive and forwarding needs explicit architecture. It belongs to Peering nontransitivity. The stated architecture instead relies on: User-defined routes can override platform routing to steer approved subnets through an NVA/firewall.
Azure Firewall provides managed stateful filtering with network/application rule models. That statement describes Azure Firewall rules, while the question asks how UDR firewall inspection works: User-defined routes can override platform routing to steer approved subnets through an NVA/firewall.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. User-defined routes can override platform routing to steer approved subnets through an NVA/firewall.
The design team completed work on SQL schema isolation. Its governing requirement was: A multitenant app needs strong tenant-level database isolation and easy tenant backup/restore. Identify the conclusive verification result.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. Confirm using the measurable result: A tenant restore does not overwrite another tenant's data.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The SQL geo-replication reporting test checks report queries use the designated secondary and replication lag stays within the accepted bound; the relevant outcome is A tenant restore does not overwrite another tenant's data.
Flexible Server provides managed MySQL compute storage and backups. The offered observation would demonstrate MySQL managed service: The application retains its MySQL driver and PITR test succeeds. The current validation is different: A tenant restore does not overwrite another tenant's data.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The distinguishing check is: A tenant restore does not overwrite another tenant's data.
A rollout addressing Azure Files snapshots has reached acceptance testing. The original problem was: An Azure Files SMB share needs hourly recovery of files accidentally overwritten by users. Which finding verifies its resolution?
Share snapshots preserve file-share point-in-time state for supported restoration. Confirm using the measurable result: An earlier version of an overwritten spreadsheet is recovered from a share snapshot.
Compute replication does not automatically guarantee complete application network reachability. The offered observation would demonstrate Azure-to-Azure ASR networking: A test failover can reach the recovered app through the intended private routes. The current validation is different: An earlier version of an overwritten spreadsheet is recovered from a share snapshot.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The distinguishing check is: An earlier version of an overwritten spreadsheet is recovered from a share snapshot.
Multi-user authorization separates approval boundaries for critical backup changes. The Multifactor critical operations test checks a destructive backup operation requires the independent authorized role; the relevant outcome is An earlier version of an overwritten spreadsheet is recovered from a share snapshot.
Architecture review: SQL ledger immutability and SQL Hyperscale growth. Requirement A: Auditors require cryptographic evidence that transaction history was not tampered with after posting. Requirement B: One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers. Which complete two-part proposal satisfies both constraints?
For requirement A, ledger records cryptographically verifiable tamper-evidence for supported relational tables. For requirement B, hyperscale decouples storage scale from compute and supports large database sizes. Verify both independently: Verification detects an altered historical ledger record during an audit; A growth test reaches the required storage target with the expected compute and backup architecture.
One action is correct. The other targets SQL managed instance compatibility, leaving SQL ledger immutability unsolved. Its necessary action is: Evaluate Azure SQL ledger tables with verifiable database digests.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Hyperscale decouples storage scale from compute and supports large database sizes. The proposed steps (consider Azure SQL Managed Instance after checking required SQL Server features; choose the SQL Business Critical service tier where the workload and availability needs justify its cost) address other capabilities instead of this required pair.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. The other proposed action (choose the SQL Business Critical service tier where the workload and availability needs justify its cost) addresses a different operation. Hyperscale decouples storage scale from compute and supports large database sizes.
Before approving Blob GZRS durability, the reviewer assesses this requirement: A critical object store needs zone resilience in primary and a regional recovery copy. Which of the reported outcomes is decisive?
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. Confirm using the measurable result: A regional recovery plan uses the secondary while zonal faults leave primary available.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The distinguishing check is: A regional recovery plan uses the secondary while zonal faults leave primary available.
Zone redundancy spreads eligible database availability replicas across zones. The offered observation would demonstrate Azure SQL zone redundancy: A zone failure does not permanently interrupt application database access. The current validation is different: A regional recovery plan uses the secondary while zonal faults leave primary available.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. Those observations validate Application Gateway zone redundancy. They do not establish the required Blob GZRS durability result: A regional recovery plan uses the secondary while zonal faults leave primary available.
Architecture rationale review—PostgreSQL read replica: Add supported PostgreSQL Flexible Server read replicas with suitable replication-lag expectations. Which explanation accurately distinguishes this capability?
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. It is material here because an application uses PostgreSQL for writes but analysts overload the writer with complex read-only reports.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. That statement describes SQL database partitioning, while the question asks how PostgreSQL read replica works: Read replicas offload eligible read-only queries but are asynchronously updated from the writer.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. Read replicas offload eligible read-only queries but are asynchronously updated from the writer.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. It belongs to PostgreSQL flexible server. The stated architecture instead relies on: Read replicas offload eligible read-only queries but are asynchronously updated from the writer.
Please check your mailbox for a message from support@examlabs.com and follow the directions.