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 solution must address both Azure SQL Database single database and SQL managed instance compatibility. First requirement: A SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems. Second requirement: A legacy SQL Server app requires SQL Agent jobs and broad instance-level compatibility during cloud migration. Select TWO recommendations that meet these independent needs.
For the Azure SQL Database single database half of this two-part design, Azure SQL Database offers fully managed relational database operations with automated backups. Verify: The application connects through its supported driver without patching database VMs. The other half concerns SQL managed instance compatibility.
For the SQL managed instance compatibility half of this design, managed Instance supports many instance-scoped SQL Server capabilities with a managed service. Check: Compatibility assessment and agent-dependent workloads complete without rewriting required instance features. The other half concerns Azure SQL Database single database.
Hyperscale decouples storage scale from compute and supports large database sizes. Its own validation would be: A growth test reaches the required storage target with the expected compute and backup architecture. The current paired requirement is Azure SQL Database single database and SQL managed instance compatibility.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. The corresponding task is SQL schema isolation: A multitenant app needs strong tenant-level database isolation and easy tenant backup/restore. It is not one of the two requested controls (Azure SQL Database single database and SQL managed instance compatibility).
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. Its own validation would be: Report queries use the designated secondary and replication lag stays within the accepted bound. The current paired requirement is Azure SQL Database single database and SQL managed instance compatibility.
During technical sign-off for Deployment drift, the architect selects: Use a what-if deployment comparison and controlled remediation for the declared configuration. Which underlying behavior should be documented?
Azure deployment what-if previews resource changes before applying a template. It is material here because a production app's manually changed resource settings diverge from the approved IaC template.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. Azure deployment what-if previews resource changes before applying a template.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. Azure deployment what-if previews resource changes before applying a template.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. That statement describes Defender compliance, while the question asks how Deployment drift works: Azure deployment what-if previews resource changes before applying a template.
Architecture rationale review—Vault network boundary: Use a Key Vault private endpoint and correctly configured private DNS and firewall policy. Which explanation accurately distinguishes this capability?
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. It is material here because a vault must be reachable only from approved private Azure networks and not from arbitrary internet clients.
Authentication strengths let Conditional Access require supported strong methods based on conditions. Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly.
App-only permissions grant service principal operations without a delegated signed-in user. That statement describes Application permissions, while the question asks how Vault network boundary works: Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly.
A proposed solution for Databricks Delta Lake is: Use Delta Lake tables on Azure Databricks with an appropriate catalog. Select the strongest statement supporting the recommendation.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. It is material here because an ETL architecture needs ACID updates and versioned tables over object storage for Spark workloads.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. That statement describes Service Bus ordering, while the question asks how Databricks Delta Lake works: Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores.
Partner event integration routes supported third-party event types without custom polling. Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores.
Mapping data flows transform data on managed Spark compute from graphical mappings. Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores.
A managed PostgreSQL server is damaged by a schema update and needs its prior state. An engineer must deliver the following acceptance evidence: A recovered server answers queries using data from before the accidental update. What design choice is defensible?
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. The selected architecture is use Flexible Server point-in-time restore within supported backup-retention limits; confirm the result by checking that a recovered server answers queries using data from before the accidental update.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. Its design target is SQL database PITR. The stated requirement instead concerns: A managed PostgreSQL server is damaged by a schema update and needs its prior state.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. It does not solve the specified PostgreSQL PITR condition.
Continuous backup can support point-in-time restore for supported Cosmos API accounts. The current need is: A managed PostgreSQL server is damaged by a schema update and needs its prior state.
A model inference service needs supported GPU acceleration and low response latency. An engineer must deliver the following acceptance evidence: The model uses available GPU memory and meets measured inference latency. What design choice is defensible?
GPU instances provide accelerators not present on standard CPU-only VMs. The selected architecture is use an Azure GPU-capable VM family compatible with the model runtime; confirm the result by checking that the model uses available GPU memory and meets measured inference latency.
Redundancy prevents a single host maintenance event from removing the only serving instance. The relevant requirement is: A model inference service needs supported GPU acceleration and low response latency.
Blue-green deployment preserves a prior known-good instance while testing a replacement. It does not solve the specified GPU VM condition.
ASE provides dedicated App Service hosting in a customer virtual-network environment. That is useful for App Service isolation (A regulated web application needs private dedicated hosting and stricter network isolation). It does not meet the current GPU VM requirement: A model inference service needs supported GPU acceleration and low response latency.
The design team completed work on Failback after recovery. Its governing requirement was: A team has documented failover to a secondary region but no controlled return to primary. Identify the conclusive verification result.
Failback is a separate operational sequence after workloads run in the recovery site. Confirm using the measurable result: A controlled failback returns traffic and state to the primary without unplanned data loss.
Immutable backup settings can prevent specified destructive operations against protected backups. The distinguishing check is: A controlled failback returns traffic and state to the primary without unplanned data loss.
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 A controlled failback returns traffic and state to the primary without unplanned data loss.
RTO is the maximum acceptable restoration duration, not the amount of lost data. The offered observation would demonstrate Recovery time objective: A regional failover test restores business service in less than the allowed interval. The current validation is different: A controlled failback returns traffic and state to the primary without unplanned data loss.
A proposed solution for Rehost versus refactor is: Choose rehosting to suitable Azure VMs as the initial migration strategy. Select the strongest statement supporting the recommendation.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. It is material here because a legacy monolith must migrate within weeks with few code changes and no supported PaaS target.
DNS cutover requires propagation and dependency planning independent of VM replication. It belongs to Networking cutover DNS. The stated architecture instead relies on: Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization.
Hidden dependencies can break after migration even when VM replication succeeds. That statement describes Application dependency mapping, while the question asks how Rehost versus refactor works: Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization.
AzCopy provides scripted high-throughput online transfers with resumability. Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization.
A Cosmos container uses a low-cardinality partition key and has hot-partition throttling. Which Azure architecture would most directly achieve the required result: RU consumption distributes across partitions and the query includes its expected partition key?
Partition key distribution governs data/throughput placement and query efficiency. The selected architecture is choose a high-cardinality partition key aligned with dominant access queries; confirm the result by checking that RU consumption distributes across partitions and the query includes its expected partition key.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. It does not solve the specified Cosmos partition key condition.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The relevant requirement is: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling.
Session consistency offers read-your-writes within a session without strong global consistency. That is useful for Cosmos session consistency (A customer portal must read its own updates while accepting that other users may briefly see stale writes). It does not meet the current Cosmos partition key requirement: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling.
The target environment adopts this approach for Blob object storage: Use Azure Blob Storage containers with lifecycle policies and scoped access. What property makes it suitable?
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. It is material here because a media service stores millions of image and video objects accessed through REST without a shared file system.
Partition key distribution governs data/throughput placement and query efficiency. Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes.
Cosmos DB provides a distributed document database with configurable consistency and throughput. Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. That statement describes Premium SSD v2, while the question asks how Blob object storage works: Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes.
A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings. An engineer must deliver the following acceptance evidence: A token-based read works and the app has no stored storage-account key. What design choice is defensible?
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The selected architecture is enable a managed identity and grant it Storage Blob Data Reader at the smallest needed scope; confirm the result by checking that a token-based read works and the app has no stored storage-account key.
Key Vault keys can perform cryptographic operations while restricting private key exposure. It does not solve the specified Managed identity for App Service condition.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. That is useful for Consumer sign-in (An external-facing consumer application requires local and social identity sign-in separate from workforce identities). It does not meet the current Managed identity for App Service requirement: A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings.
Private Link gives a private address path to supported vault endpoints when DNS resolves accordingly. The relevant requirement is: A web API on Azure App Service needs to read a storage blob without keeping client secrets in application settings.
Please check your mailbox for a message from support@examlabs.com and follow the directions.