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
An existing MySQL application needs automated patching and backups with minimal database changes. An architecture board will approve a solution only if this outcome is demonstrated: The application retains its MySQL driver and PITR test succeeds. What should be selected?
Flexible Server provides managed MySQL compute storage and backups. The selected architecture is choose Azure Database for MySQL Flexible Server after compatibility review; confirm the result by checking that the application retains its MySQL driver and PITR test succeeds.
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. It does not solve the specified MySQL managed service condition.
CMK encryption protects database data at rest while keys are managed under customer control. The current need is: An existing MySQL application needs automated patching and backups with minimal database changes.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. That is useful for SQL database monitoring (DBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier). It does not meet the current MySQL managed service requirement: An existing MySQL application needs automated patching and backups with minimal database changes.
A web service must survive loss of one data center within an Azure region. Identify the most suitable implementation for an outcome where a simulated zonal loss leaves healthy VM instances serving requests.
Availability zones isolate infrastructure failure domains within an enabled region. The selected architecture is deploy redundant VMs across availability zones behind an appropriate load balancer; confirm the result by checking that a simulated zonal loss leaves healthy VM instances serving requests.
Fault injection tests whether resilience patterns work under realistic failure conditions. It does not solve the specified Availability zones for VM tier condition.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. The current need is: A web service must survive loss of one data center within an Azure region.
Eligible App Service plans distribute app workers across availability zones with sufficient capacity. Its design target is App Service zone redundancy. The stated requirement instead concerns: A web service must survive loss of one data center within an Azure region.
A legal obligation requires recovery of relational records from a backup taken five years ago. Which Azure architecture would most directly achieve the required result: A designated five-year backup remains listed and can restore a compliant copy?
LTR retains selected full backups over years rather than only the standard short PITR window. The selected architecture is configure Azure SQL long-term retention for the required backup schedule; confirm the result by checking that a designated five-year backup remains listed and can restore a compliant copy.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The current need is: A legal obligation requires recovery of relational records from a backup taken five years ago.
Failback is a separate operational sequence after workloads run in the recovery site. That is useful for Failback after recovery (A team has documented failover to a secondary region but no controlled return to primary). It does not meet the current SQL long-term recovery requirement: A legal obligation requires recovery of relational records from a backup taken five years ago.
Share snapshots preserve file-share point-in-time state for supported restoration. It does not solve the specified SQL long-term recovery condition.
An application needs to redirect an old URL path and add a security header at the global edge without changing its origin code. Which Azure architecture would most directly achieve the required result: Requests to the deprecated path redirect and supported responses include the configured header?
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The selected architecture is use Azure Front Door rule sets for supported redirects and response-header actions; confirm the result by checking that requests to the deprecated path redirect and supported responses include the configured header.
Edge content distribution can cache static resources near users. That is useful for CDN static content (Marketing assets should be delivered from regional edge nodes instead of a central origin). It does not meet the current Front Door rules engine requirement: An application needs to redirect an old URL path and add a security header at the global edge without changing its origin code.
Event Grid distributes discrete source events to configured subscribers. It does not solve the specified Front Door rules engine condition.
Web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. The relevant requirement is: An application needs to redirect an old URL path and add a security header at the global edge without changing its origin code.
An architect must sign off on ADF tumbling window. The business problem is: A nightly ingestion job must process every hourly window and backfill missed intervals after outages. What observed test result provides valid evidence?
Tumbling-window triggers model contiguous time slices with support for backfill. Confirm using the measurable result: A missed hour is scheduled for a controlled rerun rather than silently skipped.
Serverless SQL queries external lake files with consumption-based query compute. The Synapse serverless SQL test checks a SELECT reads the Parquet dataset with no dedicated SQL pool running; the relevant outcome is A missed hour is scheduled for a controlled rerun rather than silently skipped.
Mapping data flows transform data on managed Spark compute from graphical mappings. The offered observation would demonstrate ADF mapping data flow: The pipeline produces the expected transformed dataset at planned throughput. The current validation is different: A missed hour is scheduled for a controlled rerun rather than silently skipped.
OneLake offers a common analytics data foundation for supported Fabric workloads. The distinguishing check is: A missed hour is scheduled for a controlled rerun rather than silently skipped.
A solution must address both Traffic Manager DNS routing and SQL failover groups HA. First requirement: A TCP application requires global endpoint selection using DNS without a global L7 reverse proxy. Second requirement: The database service must recover a read/write endpoint when the primary Azure region fails. Select TWO recommendations that meet these independent needs.
For the Traffic Manager DNS routing half of this two-part design, traffic Manager is DNS-based and clients connect directly to the returned service endpoint. Verify: DNS responses prefer the healthy endpoint as monitoring marks another unavailable. The other half concerns SQL failover groups HA.
For the SQL failover groups HA half of this design, failover-group listeners abstract the primary location during regional failover. Check: The app reconnects after an orchestrated failover without endpoint edits. The other half concerns Traffic Manager DNS routing.
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. This alternative solves Graceful scale-in, while the question separately requires Traffic Manager DNS routing and SQL failover groups HA.
Availability sets spread VM instances across host-related fault and update domains within a datacenter. The corresponding task is Availability set: A legacy VM workload runs in a region without required availability zones but needs protection from host maintenance faults. It is not one of the two requested controls (Traffic Manager DNS routing and SQL failover groups HA).
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. That plan is appropriate for Circuit breaker behavior. The two controls sought here are Traffic Manager DNS routing and SQL failover groups HA.
Before approving Service endpoint, the reviewer assesses this requirement: A subnet should reach Azure Storage over Azure backbone with storage firewall scoped to that subnet. Which of the reported outcomes is decisive?
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. Confirm using the measurable result: The approved subnet accesses storage and unauthorized internet clients are blocked.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. The distinguishing check is: The approved subnet accesses storage and unauthorized internet clients are blocked.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. The Application Gateway internal test checks internal clients reach /api and /web paths through the private gateway and external clients cannot; the relevant outcome is The approved subnet accesses storage and unauthorized internet clients are blocked.
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. The offered observation would demonstrate UDR firewall inspection: Traceroute and firewall logs show the intended inspected egress path. The current validation is different: The approved subnet accesses storage and unauthorized internet clients are blocked.
A legacy monolith must migrate within weeks with few code changes and no supported PaaS target. Choose the architecture that can be validated by this result: The app runs on Azure VMs with unchanged interfaces before later refactoring.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. The selected architecture is choose rehosting to suitable Azure VMs as the initial migration strategy; confirm the result by checking that the app runs on Azure VMs with unchanged interfaces before later refactoring.
AzCopy provides scripted high-throughput online transfers with resumability. That is useful for AzCopy online migration (A manageable volume of blobs must be copied over a high-bandwidth internet link with incremental reruns). It does not meet the current Rehost versus refactor requirement: A legacy monolith must migrate within weeks with few code changes and no supported PaaS target.
Hidden dependencies can break after migration even when VM replication succeeds. Its design target is Application dependency mapping. The stated requirement instead concerns: 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 does not solve the specified Rehost versus refactor condition.
A connectivity failure may be caused by either NSG rules, routing or the remote endpoint. A deployment must satisfy this operational criterion: The test identifies the blocking NSG rule or unreachable next hop before changing production routes. Which plan is appropriate?
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. The selected architecture is use Network Watcher connection troubleshoot and IP flow verify where supported; confirm the result by checking that the test identifies the blocking NSG rule or unreachable next hop before changing production routes.
VNet integration is principally an outbound feature; inbound private access requires other controls. Its design target is VNet integration App Service. The stated requirement instead concerns: A connectivity failure may be caused by either NSG rules, routing or the remote endpoint.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. The relevant requirement is: A connectivity failure may be caused by either NSG rules, routing or the remote endpoint.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. It does not solve the specified Network Watcher diagnosis condition.
The acceptance criterion for Fabric OneLake analytics comes from this issue: A company wants shared analytics data products for Lakehouse and Warehouse consumers in one SaaS environment. Which measured outcome is the strongest proof?
OneLake offers a common analytics data foundation for supported Fabric workloads. Confirm using the measurable result: Authorized Fabric consumers query the shared curated data with governed access.
Partner event integration routes supported third-party event types without custom polling. The offered observation would demonstrate Event Grid partner events: A partner-created event triggers only matching subscriptions across the consuming applications. The current validation is different: Authorized Fabric consumers query the shared curated data with governed access.
A stored watermark limits reads to changes after the last successful processed interval. Those observations validate ADF incremental copy. They do not establish the required Fabric OneLake analytics result: Authorized Fabric consumers query the shared curated data with governed access.
Pipeline control flow can orchestrate dependent stages instead of independent schedules. The distinguishing check is: Authorized Fabric consumers query the shared curated data with governed access.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.