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 business-critical file repository must survive an availability-zone outage without a regional failover. Which Azure architecture would most directly achieve the required result: Reading and writing a test blob continues while one zone is unavailable?
ZRS synchronously replicates data across primary-region zones. The selected architecture is choose zone-redundant storage where the account and service support it; confirm the result by checking that reading and writing a test blob continues while one zone is unavailable.
Read regions bring replicas closer to users without inherently adding multi-write semantics. The current need is: A business-critical file repository must survive an availability-zone outage without a regional failover.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. That is useful for Application Gateway zone redundancy (A web workload requires HTTP routing and WAF across availability zones). It does not meet the current Blob ZRS availability requirement: A business-critical file repository must survive an availability-zone outage without a regional failover.
Zone-distributed nodes plus suitable Kubernetes scheduling reduce single-zone concentration. It does not solve the specified Blob ZRS availability condition.
The design team completed work on Point-to-site VPN. Its governing requirement was: Remote administrators need individually authenticated encrypted connectivity to Azure private resources. Identify the conclusive verification result.
Point-to-site VPN authenticates individual clients for private network access. Confirm using the measurable result: Authorized clients connect privately and revoked clients cannot establish a tunnel.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. The distinguishing check is: Authorized clients connect privately and revoked clients cannot establish a tunnel.
Private DNS zone links determine name resolution for VNets that consume private endpoints. The DNS private zones test checks a lookup from the spoke resolves the service FQDN to the intended private IP; the relevant outcome is Authorized clients connect privately and revoked clients cannot establish a tunnel.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Those observations validate ExpressRoute private circuit. They do not establish the required Point-to-site VPN result: Authorized clients connect privately and revoked clients cannot establish a tunnel.
A solution must address both SQL auditing and SQL customer-managed keys. First requirement: Compliance requires records of login attempts and selected database actions independent of app logs. Second requirement: Compliance requires the SQL database encryption protector to use customer-controlled key lifecycle in Key Vault. Select TWO recommendations that meet these independent needs.
For the SQL auditing half of this two-part design, SQL auditing captures database events as configured separately from application request telemetry. Verify: A controlled login and database action appear in the configured audit destination. The other half concerns SQL customer-managed keys.
For the SQL customer-managed keys half of this design, CMK encryption protects database data at rest while keys are managed under customer control. Check: The database reports the approved key as its TDE protector and follows documented key rotation. The other half concerns SQL auditing.
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 SQL auditing and SQL customer-managed keys.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. The corresponding task is SQL managed instance compatibility: A legacy SQL Server app requires SQL Agent jobs and broad instance-level compatibility during cloud migration. It is not one of the two requested controls (SQL auditing and SQL customer-managed keys).
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. Its own validation would be: A tenant restore does not overwrite another tenant's data. The current paired requirement is SQL auditing and SQL customer-managed keys.
The design team completed work on SQL geo-restore. Its governing requirement was: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Identify the conclusive verification result.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. Confirm using the measurable result: A region-loss exercise recovers a database from the latest supported geo backup.
Nightly backups alone do not provide continuous workload replication or low recovery time. The offered observation would demonstrate Backup versus DR: The DR drill meets recovery objectives while backup restore still supports historical rollback. The current validation is different: A region-loss exercise recovers a database from the latest supported geo backup.
Compute replication does not automatically guarantee complete application network reachability. The distinguishing check is: A region-loss exercise recovers a database from the latest supported geo backup.
RPO measures the maximum tolerated data loss period at a recovery point. The Recovery point objective test checks failover comparison shows the latest committed recoverable write is within five minutes; the relevant outcome is A region-loss exercise recovers a database from the latest supported geo backup.
Architecture review: AKS container diagnosis and Network-flow telemetry. Requirement A: An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health. Requirement B: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture. Which complete two-part proposal satisfies both constraints?
For requirement A, container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. For requirement B, virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. Verify both independently: The restarting pod and its container events are visible with node and namespace context; A blocked test connection is correlated with its source destination and flow disposition.
Both proposed halves address other use cases: VM resource health and Cross-subscription workspace. The requested pair is AKS container diagnosis and Network-flow telemetry.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. The other proposed action (use Azure Resource Health and resource health alerts for the VM) does not implement the first control. Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics.
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. The other proposed action (send supported resource logs from each subscription into a centralized Log Analytics workspace) addresses a different operation. Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights.
Legacy apps require on-premises Active Directory-integrated authentication while using Azure for modern services. An engineer must deliver the following acceptance evidence: A test legacy app authenticates with its required protocol while cloud resources use Entra controls. What design choice is defensible?
Hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure. The selected architecture is design supported hybrid identity integration for the existing Active Directory dependency; confirm the result by checking that a test legacy app authenticates with its required protocol while cloud resources use Entra controls.
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 On-prem AD federation requirement: Legacy apps require on-premises Active Directory-integrated authentication while using Azure for modern services.
Management locks guard against accidental resource deletes and operate separately from authorization roles. Its design target is Resource lock constraints. The stated requirement instead concerns: Legacy apps require on-premises Active Directory-integrated authentication while using Azure for modern services.
Administrative units scope eligible directory management roles to selected objects, not data visibility. It does not solve the specified On-prem AD federation condition.
Before approving Standardized IaC, the reviewer assesses this requirement: Operations wants reproducible Azure environment deployments from version-controlled definitions. Which of the reported outcomes is decisive?
Infrastructure as code declares desired resources and allows review and repeat deployment. Confirm using the measurable result: The same versioned module deploys matching compliant resources across test environments.
Landing zones combine platform foundations with repeatable application subscription governance. The Landing zones test checks new app subscriptions start with baseline policies, connectivity and logging; the relevant outcome is The same versioned module deploys matching compliant resources across test environments.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. The offered observation would demonstrate Defender compliance: A noncompliant resource is reported under the relevant regulatory control. The current validation is different: The same versioned module deploys matching compliant resources across test environments.
Azure Policy can deny targeted resource types without revoking all contributor operations. The distinguishing check is: The same versioned module deploys matching compliant resources across test environments.
An architect must sign off on Database resource diagnostics. The business problem is: A SQL database writes audit and performance diagnostics but the central workspace has only platform activity records. What observed test result provides valid evidence?
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. Confirm using the measurable result: SQL diagnostic records appear in the target workspace and can be filtered by database name.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. The offered observation would demonstrate WAF decision logs: A blocked test request identifies its matching WAF rule and client context in the destination logs. The current validation is different: SQL diagnostic records appear in the target workspace and can be filtered by database name.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. Those observations validate Private observability. They do not establish the required Database resource diagnostics result: SQL diagnostic records appear in the target workspace and can be filtered by database name.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The distinguishing check is: SQL diagnostic records appear in the target workspace and can be filtered by database name.
Architecture review: SQL online migration and Rehost versus refactor. Requirement A: A high-volume database allows little cutover downtime and must synchronize changes before switch. Requirement B: A legacy monolith must migrate within weeks with few code changes and no supported PaaS target. Which complete two-part proposal satisfies both constraints?
For requirement A, online migration reduces cutover downtime by applying ongoing changes after the baseline copy. For requirement B, rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. Verify both independently: Source and target reconcile and final cutover falls within the tolerated outage; The app runs on Azure VMs with unchanged interfaces before later refactoring.
One action is correct. The other targets Hybrid route validation, leaving Rehost versus refactor unsolved. Its necessary action is: Choose rehosting to suitable Azure VMs as the initial migration strategy.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. The other proposed action (plan an incremental refactor into bounded services with asynchronous integration) does not implement the first control. Online migration reduces cutover downtime by applying ongoing changes after the baseline copy.
This combines Refactor monolith and Hybrid route validation, which do not satisfy the distinct requirements for SQL online migration and Rehost versus refactor.
An architect must sign off on Backup soft delete. The business problem is: An operator deletes a backup item by mistake and must recover its protected points before permanent purge. What observed test result provides valid evidence?
Soft delete retains recoverable protected backup data after deletion for a configured interval. Confirm using the measurable result: The deleted item is recoverable within the protected deletion window.
Failback is a separate operational sequence after workloads run in the recovery site. The distinguishing check is: The deleted item is recoverable within the protected deletion window.
Periodic backups produce interval snapshots and are not the same as continuous point-in-time recovery. The Cosmos periodic backup test checks the new design demonstrates recovery granularity consistent with the RPO; the relevant outcome is The deleted item is recoverable within the protected deletion window.
Independent crash-consistent snapshots may not preserve database write ordering across disks. Those observations validate Disk snapshot consistency. They do not establish the required Backup soft delete result: The deleted item is recoverable within the protected deletion window.
The design team completed work on Cross-subscription workspace. Its governing requirement was: Four subscriptions must be searched together during incident response with one KQL query and shared retention policy. Identify the conclusive verification result.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. Confirm using the measurable result: The same query returns events labeled with all four source subscription IDs.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. The offered observation would demonstrate WAF decision logs: A blocked test request identifies its matching WAF rule and client context in the destination logs. The current validation is different: The same query returns events labeled with all four source subscription IDs.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. Those observations validate Network-flow telemetry. They do not establish the required Cross-subscription workspace result: The same query returns events labeled with all four source subscription IDs.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The distinguishing check is: The same query returns events labeled with all four source subscription IDs.
Please check your mailbox for a message from support@examlabs.com and follow the directions.