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
Architecture review: SQL database PITR and SQL geo-restore. Requirement A: A deployment accidentally truncates a transaction table and the database must be recovered before the change. Requirement B: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure SQL automatic full differential and log backups support restoring database state at a selected time. For requirement B, geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. Verify both independently: A restored database contains transactions immediately preceding the truncation; A region-loss exercise recovers a database from the latest supported geo backup.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The proposed steps (assign scoped backup roles with least privilege and protected operation controls; evaluate continuous-backup mode if precise PITR is a firm requirement) address other capabilities instead of this required pair.
The first step implements Backup vault access instead of SQL database PITR. The necessary change is to use managed Azure SQL point-in-time restore to a new database within backup retention.
The option covers one requirement but substitutes Cosmos periodic backup for SQL geo-restore. The missing acceptance result is: A region-loss exercise recovers a database from the latest supported geo backup.
The Azure Cache for Redis review proposes: Use a managed Azure Redis-compatible cache with invalidation and TTL design. Which Azure behavior is the technical justification for this decision?
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. It is material here because a read-heavy catalog repeatedly queries relational data for identical frequently accessed results.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled.
Blob change feed records changes to blob objects for downstream processing. An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. It belongs to Premium SSD v2. The stated architecture instead relies on: An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled.
For the SQL failover groups HA requirement, the proposed architecture uses: Configure Azure SQL failover groups and an app connection using the appropriate listener. Why does that design fit?
Failover-group listeners abstract the primary location during regional failover. It is material here because the database service must recover a read/write endpoint when the primary Azure region fails.
Zone redundancy spreads eligible database availability replicas across zones. Failover-group listeners abstract the primary location during regional failover.
A zone-separated standby supports automated failover where offered. That statement describes PostgreSQL zone redundant HA, while the question asks how SQL failover groups HA works: Failover-group listeners abstract the primary location during regional failover.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. Failover-group listeners abstract the primary location during regional failover.
During technical sign-off for Cosmos continuous backup, the architect selects: Use Cosmos DB continuous backup mode with appropriate restore capabilities. Which underlying behavior should be documented?
Continuous backup can support point-in-time restore for supported Cosmos API accounts. It is material here because a developer deletes Cosmos DB documents and needs to restore the account to an earlier instant.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. It belongs to SQL geo-restore. The stated architecture instead relies on: Continuous backup can support point-in-time restore for supported Cosmos API accounts.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. Continuous backup can support point-in-time restore for supported Cosmos API accounts.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. Continuous backup can support point-in-time restore for supported Cosmos API accounts.
Before approving Application dependency mapping, the reviewer assesses this requirement: A business app appears self-contained but batch jobs communicate with undocumented on-prem systems. Which of the reported outcomes is decisive?
Hidden dependencies can break after migration even when VM replication succeeds. Confirm using the measurable result: A test workload executes its dependent calls from the planned Azure subnet.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. The offered observation would demonstrate VM agentless migration: A test migration boots the replicated VM and validates application dependencies. The current validation is different: A test workload executes its dependent calls from the planned Azure subnet.
Refactoring changes application structure and decouples independent workloads. Those observations validate Refactor monolith. They do not establish the required Application dependency mapping result: A test workload executes its dependent calls from the planned Azure subnet.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. The distinguishing check is: A test workload executes its dependent calls from the planned Azure subnet.
A multitenant app needs strong tenant-level database isolation and easy tenant backup/restore. Choose the architecture that can be validated by this result: A tenant restore does not overwrite another tenant's data.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. The selected architecture is use one managed database per tenant when isolation and lifecycle needs outweigh extra operations; confirm the result by checking that a tenant restore does not overwrite another tenant's data.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. The current need is: A multitenant app needs strong tenant-level database isolation and easy tenant backup/restore.
CMK encryption protects database data at rest while keys are managed under customer control. It does not solve the specified SQL schema isolation condition.
An elastic pool can share compute across independent Azure SQL databases, but it does not automatically create a separate data or restore boundary for each tenant inside one shared database. This option deliberately puts all tenant records into one database, leaving the required tenant-by-tenant restore isolation unmet. Option A explicitly gives each tenant its own database and recovery unit.
A solution must address both UDR firewall inspection and Service endpoint. First requirement: A subnet must send internet-bound flows through a centrally managed inspection firewall. Second requirement: A subnet should reach Azure Storage over Azure backbone with storage firewall scoped to that subnet. Select TWO recommendations that meet these independent needs.
For the Service endpoint half of this design, service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. Check: The approved subnet accesses storage and unauthorized internet clients are blocked. The other half concerns UDR firewall inspection.
For the UDR firewall inspection half of this two-part design, user-defined routes can override platform routing to steer approved subnets through an NVA/firewall. Verify: Traceroute and firewall logs show the intended inspected egress path. The other half concerns Service endpoint.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. That plan is appropriate for Network Watcher diagnosis. The two controls sought here are UDR firewall inspection and Service endpoint.
DDoS protection adds adaptive mitigation and telemetry for supported public resources. This alternative solves DDoS protection, while the question separately requires UDR firewall inspection and Service endpoint.
Private endpoints provide a private inbound path for supported App Service access. The corresponding task is Private inbound App Service: An App Service must accept requests only through the corporate private network. It is not one of the two requested controls (UDR firewall inspection and Service endpoint).
Architecture review: Application dependency mapping and Azure Migrate inventory. Requirement A: A business app appears self-contained but batch jobs communicate with undocumented on-prem systems. Requirement B: An on-prem estate has hundreds of VMs and architects need dependency-aware discovery before sizing Azure. Which complete two-part proposal satisfies both constraints?
For requirement A, hidden dependencies can break after migration even when VM replication succeeds. For requirement B, Azure Migrate inventories servers and supports readiness and sizing assessments. Verify both independently: A test workload executes its dependent calls from the planned Azure subnet; Assessment lists discovered servers, interdependencies and estimated Azure sizing.
One action is correct. The other targets SQL offline migration, leaving Application dependency mapping unsolved. Its necessary action is: Build a dependency map and classify blockers before sequencing migration waves.
This combines SQL offline migration and SQL online migration, which do not satisfy the distinct requirements for Application dependency mapping and Azure Migrate inventory.
The option covers one requirement but substitutes SQL online migration for Azure Migrate inventory. The missing acceptance result is: Assessment lists discovered servers, interdependencies and estimated Azure sizing.
Architecture review: SQL Always Encrypted and SQL customer-managed keys. Requirement A: A database handles patient identifiers that should stay encrypted from database administrators during normal access. Requirement B: Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault. Which complete two-part proposal satisfies both constraints?
For requirement A, always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. For requirement B, CMK encryption protects database data at rest while keys are managed under customer control. Verify both independently: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values; The database reports the approved key as its TDE protector and follows documented key rotation.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. CMK encryption protects database data at rest while keys are managed under customer control. The proposed steps (use SQL system-versioned temporal tables with appropriate retention and permissions; configure supported Azure SQL active geo-replication and route stale-tolerant reads to the replica) address other capabilities instead of this required pair.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. The other proposed action (configure supported Azure SQL active geo-replication and route stale-tolerant reads to the replica) addresses a different operation. CMK encryption protects database data at rest while keys are managed under customer control.
The option covers one requirement but substitutes SQL temporal tables for SQL Always Encrypted. The missing acceptance result is: The client retrieves authorized plaintext while a privileged server-side query sees encrypted values.
A globally distributed app stores schemaless JSON records at high scale with flexible document queries. Choose the architecture that can be validated by this result: The app reads JSON documents across the planned partitions with predictable latency.
Cosmos DB provides a distributed document database with configurable consistency and throughput. The selected architecture is choose Azure Cosmos DB for NoSQL with suitable partition and consistency design; confirm the result by checking that the app reads JSON documents across the planned partitions with predictable latency.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The relevant requirement is: A globally distributed app stores schemaless JSON records at high scale with flexible document queries.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. The current need is: A globally distributed app stores schemaless JSON records at high scale with flexible document queries.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. It does not solve the specified Cosmos DB NoSQL condition.
For the Cross-region backup requirement, the proposed architecture uses: Select an appropriate geo-redundant backup vault and validate cross-region restore eligibility. Why does that design fit?
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. It is material here because an organization requires VM backup copies surviving the loss of an entire Azure region.
Backup-specific RBAC roles separate operational restore tasks from vault administration. Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings.
Compute replication does not automatically guarantee complete application network reachability. It belongs to Azure-to-Azure ASR networking. The stated architecture instead relies on: Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. That statement describes Blob operational backup, while the question asks how Cross-region backup works: Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings.
Please check your mailbox for a message from support@examlabs.com and follow the directions.