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 architect must sign off on Blob versioning. The business problem is: A file is frequently overwritten and teams need to restore the value before the last upload. What observed test result provides valid evidence?
Versioning preserves older object versions independently of current content overwrites. Confirm using the measurable result: A previous version can be enumerated and restored after an accidental update.
Immutable storage prevents overwrite and delete during the configured retention interval. The Blob immutability test checks an authorized user cannot modify a protected retained object before expiry; the relevant outcome is A previous version can be enumerated and restored after an accidental update.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. The offered observation would demonstrate Cosmos conflict handling: A controlled simultaneous update resolves according to the documented business rule. The current validation is different: A previous version can be enumerated and restored after an accidental update.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The distinguishing check is: A previous version can be enumerated and restored after an accidental update.
A solution must address both On-prem AD federation and Azure Files identity access. First requirement: Legacy apps require on-premises Active Directory-integrated authentication while using Azure for modern services. Second requirement: Windows clients must access Azure Files using on-premises AD identities and SMB permissions. Select TWO recommendations that meet these independent needs.
For the Azure Files identity access half of this design, Azure Files can integrate with supported directory-based SMB authentication while share and NTFS ACLs govern access. Check: Approved domain users mount the share and unauthorized users fail the access test. The other half concerns On-prem AD federation.
For the On-prem AD federation half of this two-part design, hybrid identity connects on-prem directories and cloud identity but legacy protocols may need separate infrastructure. Verify: A test legacy app authenticates with its required protocol while cloud resources use Entra controls. The other half concerns Azure Files identity access.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The corresponding task is Resource lock constraints: An application owner accidentally deletes resources but granting Reader would block legitimate configuration changes. It is not one of the two requested controls (On-prem AD federation and Azure Files identity access).
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. That plan is appropriate for Key Vault certificate lifecycle. The two controls sought here are On-prem AD federation and Azure Files identity access.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Its own validation would be: The regional admin can reset an assigned user's password but cannot administer an out-of-scope user. The current paired requirement is On-prem AD federation and Azure Files identity access.
During technical sign-off for SQL temporal tables, the architect selects: Use SQL system-versioned temporal tables with appropriate retention and permissions. Which underlying behavior should be documented?
Temporal tables retain row history and support as-of queries independently of whole-database backups. It is material here because a finance table must retain previous versions of individual business records for an audit query.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. Temporal tables retain row history and support as-of queries independently of whole-database backups.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. It belongs to SQL schema isolation. The stated architecture instead relies on: Temporal tables retain row history and support as-of queries independently of whole-database backups.
Read-only replicas can offload reporting from the primary where the tier provides the capability. Temporal tables retain row history and support as-of queries independently of whole-database backups.
An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests. An architecture board will approve a solution only if this outcome is demonstrated: The app connects to private SQL via VNet while its public frontend remains reachable as intended. What should be selected?
VNet integration is principally an outbound feature; inbound private access requires other controls. The selected architecture is use App Service regional VNet integration for outbound connectivity and private routing; confirm the result by checking that the app connects to private SQL via VNet while its public frontend remains reachable as intended.
VPN Gateway can establish encrypted IPsec tunnels over public networks. That is useful for Site-to-site VPN (A small branch needs encrypted connectivity to a VNet over its existing internet link). It does not meet the current VNet integration App Service requirement: An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Its design target is NSG subnet filtering. The stated requirement instead concerns: An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests.
A hub centralizes connectivity services while spoke VNets isolate applications. It does not solve the specified VNet integration App Service condition.
To validate the Inherited tagging deployment, reviewers revisit this operational need: Projects repeatedly omit the environment tag although the parent resource group has it. What result confirms it was met?
Modify effects can update eligible metadata and require the required remediation permissions. Confirm using the measurable result: New supported resources inherit the resource-group environment tag after assignment.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The Role assignment scope test checks the engineer can change the assigned network group but not another group's resources; the relevant outcome is New supported resources inherit the resource-group environment tag after assignment.
Cost exports provide detailed recurring usage data for downstream allocation reporting. The offered observation would demonstrate Cost export: A monthly export lands in the correct storage path with resource and cost fields. The current validation is different: New supported resources inherit the resource-group environment tag after assignment.
Infrastructure as code declares desired resources and allows review and repeat deployment. The distinguishing check is: New supported resources inherit the resource-group environment tag after assignment.
A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port. An architecture board will approve a solution only if this outcome is demonstrated: The scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions. What should be selected?
Self-hosted integration runtime initiates supported outbound communications to access private sources. The selected architecture is use Azure Data Factory with a self-hosted integration runtime and Copy activity; confirm the result by checking that the scheduled copy reads on-premises data and lands it in the lake without inbound firewall exceptions.
OneLake offers a common analytics data foundation for supported Fabric workloads. The relevant requirement is: A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port.
Serverless SQL queries external lake files with consumption-based query compute. It does not solve the specified Data Factory hybrid copy condition.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. That is useful for Databricks Delta Lake (An ETL architecture needs ACID updates and versioned tables over object storage for Spark workloads). It does not meet the current Data Factory hybrid copy requirement: A nightly pipeline must copy on-premises SQL data to Azure Data Lake without opening an inbound corporate firewall port.
A solution must address both Route Server dynamic routing and Peering nontransitivity. First requirement: A hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn. Second requirement: Spoke A peers with the hub and spoke B peers with the same hub but cannot communicate directly. Select TWO recommendations that meet these independent needs.
For the Peering nontransitivity half of this design, vNet peering alone is not transitive and forwarding needs explicit architecture. Check: Permitted spoke-to-spoke traffic follows inspected hub path and denied traffic fails. The other half concerns Route Server dynamic routing.
For the Route Server dynamic routing half of this two-part design, route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. Verify: New approved NVA routes propagate to effective routes for attached workloads. The other half concerns Peering nontransitivity.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The corresponding task is Load Balancer internal L4: A TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes. It is not one of the two requested controls (Route Server dynamic routing and Peering nontransitivity).
Private endpoints provide a private inbound path for supported App Service access. That plan is appropriate for Private inbound App Service. The two controls sought here are Route Server dynamic routing and Peering nontransitivity.
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. This alternative solves ExpressRoute private circuit, while the question separately requires Route Server dynamic routing and Peering nontransitivity.
The target environment adopts this approach for DDoS protection: Evaluate Azure DDoS Network Protection for eligible public IPs and VNets. What property makes it suitable?
DDoS protection adds adaptive mitigation and telemetry for supported public resources. It is material here because a publicly reachable application needs additional DDoS mitigation beyond basic platform protections.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. That statement describes Application Gateway internal, while the question asks how DDoS protection works: DDoS protection adds adaptive mitigation and telemetry for supported public resources.
VNet integration is principally an outbound feature; inbound private access requires other controls. DDoS protection adds adaptive mitigation and telemetry for supported public resources.
VPN Gateway can establish encrypted IPsec tunnels over public networks. DDoS protection adds adaptive mitigation and telemetry for supported public resources.
The design team completed work on Rehost versus refactor. Its governing requirement was: A legacy monolith must migrate within weeks with few code changes and no supported PaaS target. Identify the conclusive verification result.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. Confirm using the measurable result: The app runs on Azure VMs with unchanged interfaces before later refactoring.
DNS cutover requires propagation and dependency planning independent of VM replication. The offered observation would demonstrate Networking cutover DNS: Clients resolve the new endpoint and the rollback procedure returns traffic if needed. The current validation is different: The app runs on Azure VMs with unchanged interfaces before later refactoring.
Hidden dependencies can break after migration even when VM replication succeeds. Those observations validate Application dependency mapping. They do not establish the required Rehost versus refactor result: The app runs on Azure VMs with unchanged interfaces before later refactoring.
AzCopy provides scripted high-throughput online transfers with resumability. The distinguishing check is: The app runs on Azure VMs with unchanged interfaces before later refactoring.
Architecture rationale review—Blob GZRS durability: Select GZRS or RA-GZRS based on read access needs and service support. Which explanation accurately distinguishes this capability?
GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region. It is material here because a critical object store needs zone resilience in primary and a regional recovery copy.
Zone redundancy spreads eligible database availability replicas across zones. GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region.
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region.
Circuit breakers stop futile downstream calls temporarily and permit controlled re-entry. It belongs to Circuit breaker behavior. The stated architecture instead relies on: GZRS synchronously spreads primary copies across zones and asynchronously replicates to another region.
The design team completed work on App Service web. Its governing requirement was: An HTTP API needs custom deployment slots and managed PaaS hosting without a Kubernetes operations team. Identify the conclusive verification result.
App Service manages web hosting and supports deployment slots on eligible plans. Confirm using the measurable result: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
VMSS automates management and scaling of similar VMs in the same workload. Those observations validate VMSS dynamic scaling. They do not establish the required App Service web result: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
GPU instances provide accelerators not present on standard CPU-only VMs. The distinguishing check is: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
Encryption sets connect managed disk encryption to customer-owned keys. The offered observation would demonstrate VM disk encryption: Disk configuration shows the designated key and encrypted state before production traffic. The current validation is different: Traffic swaps to a warmed-up deployment slot without SSH management of app hosts.
Please check your mailbox for a message from support@examlabs.com and follow the directions.