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
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.
The acceptance criterion for PostgreSQL migration comes from this issue: A self-managed PostgreSQL database needs transfer to Azure's managed PostgreSQL service. Which measured outcome is the strongest proof?
PostgreSQL migration requires extension, version and connectivity compatibility checks. Confirm using the measurable result: The database app passes read/write tests against the target flexible server.
Replatforming changes hosting characteristics while preserving most app behavior. The offered observation would demonstrate Replatform database: Migration validation shows required database features function on the selected managed tier. The current validation is different: The database app passes read/write tests against the target flexible server.
Object count alone cannot establish content integrity or ACL preservation. The distinguishing check is: The database app passes read/write tests against the target flexible server.
Target compatibility determines whether code changes or a different managed target are required. The Database schema assessment test checks the assessment reports blocking SQL features and chosen remediation before migration; the relevant outcome is The database app passes read/write tests against the target flexible server.
During technical sign-off for Storage service endpoints, the architect selects: Evaluate storage service endpoints with service firewall rules when Private Link isn't required. Which underlying behavior should be documented?
Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service. It is material here because virtual network workloads need storage traffic to use Azure backbone but the storage service remains publicly addressable.
Blob change feed records changes to blob objects for downstream processing. Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service.
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. It belongs to Blob user-delegation SAS. The stated architecture instead relies on: Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service.
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. That statement describes Azure Files SMB, while the question asks how Storage service endpoints works: Service endpoints secure selected Azure service traffic from VNets but do not create a private IP for the PaaS service.
A solution must address both Azure Front Door caching and Front Door rules engine. First requirement: A global website serves the same static assets to users on several continents. Second requirement: An application needs to redirect an old URL path and add a security header at the global edge without changing its origin code. Select TWO recommendations that meet these independent needs.
For the Azure Front Door caching half of this two-part design, edge caching reduces origin load and latency for eligible cacheable content. Verify: A repeat request from a distant location is served from the edge cache. The other half concerns Front Door rules engine.
For the Front Door rules engine half of this design, Front Door rule sets change eligible request and response behavior at the edge according to match conditions. Check: Requests to the deprecated path redirect and supported responses include the configured header. The other half concerns Azure Front Door caching.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. That plan is appropriate for Event Hubs telemetry. The two controls sought here are Azure Front Door caching and Front Door rules engine.
An API gateway can broker external requests to private backends without direct public backend access. This alternative solves API private backends, while the question separately requires Azure Front Door caching and Front Door rules engine.
Topics fan out a message to independently managed subscriptions with durable handling. That plan is appropriate for Publish subscribe topics. The two controls sought here are Azure Front Door caching and Front Door rules engine.
Architecture review: SQL managed instance compatibility and SQL Server on Azure VM. Requirement A: A legacy SQL Server app requires SQL Agent jobs and broad instance-level compatibility during cloud migration. Requirement B: A database application depends on a third-party kernel-level driver installed alongside SQL Server. Which complete two-part proposal satisfies both constraints?
For requirement A, managed Instance supports many instance-scoped SQL Server capabilities with a managed service. For requirement B, iaaS retains operating-system and SQL instance control that PaaS databases do not provide. Verify both independently: Compatibility assessment and agent-dependent workloads complete without rewriting required instance features; The vendor driver runs on the VM while maintenance responsibilities are explicitly assigned.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The proposed steps (select Azure SQL Database for the managed individual database; choose Azure Database for MySQL Flexible Server after compatibility review) address other capabilities instead of this required pair.
The first step implements Azure SQL Database single database instead of SQL managed instance compatibility. The necessary change is to consider Azure SQL Managed Instance after checking required SQL Server features.
One action is correct. The other targets MySQL managed service, leaving SQL Server on Azure VM unsolved. Its necessary action is: Keep SQL Server on an Azure virtual machine with appropriate HA and backup architecture.
A rollout addressing Cosmos continuous backup has reached acceptance testing. The original problem was: A developer deletes Cosmos DB documents and needs to restore the account to an earlier instant. Which finding verifies its resolution?
Continuous backup can support point-in-time restore for supported Cosmos API accounts. Confirm using the measurable result: A restored account contains the pre-deletion documents at the chosen restore timestamp.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. Those observations validate PostgreSQL PITR. They do not establish the required Cosmos continuous backup result: A restored account contains the pre-deletion documents at the chosen restore timestamp.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The distinguishing check is: A restored account contains the pre-deletion documents at the chosen restore timestamp.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. The Azure VM backup policy test checks a file-level restore recovers the deleted content from the appropriate recovery point; the relevant outcome is A restored account contains the pre-deletion documents at the chosen restore timestamp.
Architecture review: Blob versioning and Blob change feed. Requirement A: A file is frequently overwritten and teams need to restore the value before the last upload. Requirement B: An integration service needs an ordered log of changes to objects without scanning containers every minute. Which complete two-part proposal satisfies both constraints?
For requirement A, versioning preserves older object versions independently of current content overwrites. For requirement B, blob change feed records changes to blob objects for downstream processing. Verify both independently: A previous version can be enumerated and restored after an accidental update; The consumer reads expected object creation and deletion change records.
Both proposed halves address other use cases: Cosmos DB NoSQL and Cosmos session consistency. The requested pair is Blob versioning and Blob change feed.
The mismatched half is Cosmos session consistency; Blob change feed instead needs: Enable the Blob change feed for supported storage accounts.
The first step implements Cosmos DB NoSQL instead of Blob versioning. The necessary change is to enable Blob versioning with retention controls.
For the Application permissions requirement, the proposed architecture uses: Use application permissions with admin consent and an appropriate confidential credential or federation. Why does that design fit?
App-only permissions grant service principal operations without a delegated signed-in user. It is material here because a scheduled daemon must call Microsoft Graph without an interactive user session.
Management locks guard against accidental resource deletes and operate separately from authorization roles. It belongs to Resource lock constraints. The stated architecture instead relies on: App-only permissions grant service principal operations without a delegated signed-in user.
B2B collaboration supports guest principals and cross-organization access controls. That statement describes External B2B partner, while the question asks how Application permissions works: App-only permissions grant service principal operations without a delegated signed-in user.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. App-only permissions grant service principal operations without a delegated signed-in user.
The team has justified its Azure managed disks design with: Use an appropriate Azure Managed Disk SKU with latency and IOPS sizing. Which statement accurately describes why the approach works?
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. It is material here because an Azure VM runs a database requiring block device storage attached as a virtual disk.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. That statement describes ADLS ACLs, while the question asks how Azure managed disks works: Managed disks provide block storage to Azure VMs rather than object or SMB interfaces.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. Managed disks provide block storage to Azure VMs rather than object or SMB interfaces.
Immutable storage prevents overwrite and delete during the configured retention interval. It belongs to Blob immutability. The stated architecture instead relies on: Managed disks provide block storage to Azure VMs rather than object or SMB interfaces.
A solution must address both Container Registry and VM disk encryption. First requirement: Build pipelines need a private managed Docker image repository with vulnerability scanning and managed identity access. Second requirement: A finance VM needs customer-managed encryption keys for managed disks. Select TWO recommendations that meet these independent needs.
For the Container Registry half of this two-part design, ACR stores OCI images and supports Azure identity-based authorization to the registry. Verify: A pipeline pushes a signed image and production pulls it without shared registry passwords. The other half concerns VM disk encryption.
For the VM disk encryption half of this design, encryption sets connect managed disk encryption to customer-owned keys. Check: Disk configuration shows the designated key and encrypted state before production traffic. The other half concerns Container Registry.
Dedicated Host provides physical host isolation with separate placement and pricing controls. The corresponding task is Dedicated host: A regulated app requires a physically dedicated server host for VM placement and host-level isolation. It is not one of the two requested controls (Container Registry and VM disk encryption).
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. Its own validation would be: A matching event triggers the function within the required processing window. The current paired requirement is Container Registry and VM disk encryption.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. This alternative solves Autoscaling based on queue, while the question separately requires Container Registry and VM disk encryption.
For the Stream Analytics window requirement, the proposed architecture uses: Use Azure Stream Analytics with an appropriate time window query. Why does that design fit?
Stream Analytics supports SQL-like processing over streaming sources with time windows. It is material here because a telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code.
Self-hosted integration runtime initiates supported outbound communications to access private sources. Stream Analytics supports SQL-like processing over streaming sources with time windows.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. It belongs to Private integration access. The stated architecture instead relies on: Stream Analytics supports SQL-like processing over streaming sources with time windows.
Partner event integration routes supported third-party event types without custom polling. Stream Analytics supports SQL-like processing over streaming sources with time windows.
Please check your mailbox for a message from support@examlabs.com and follow the directions.