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 hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn. An architecture board will approve a solution only if this outcome is demonstrated: New approved NVA routes propagate to effective routes for attached workloads. What should be selected?
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. The selected architecture is use Azure Route Server to exchange BGP routes with a supported NVA; confirm the result by checking that new approved NVA routes propagate to effective routes for attached workloads.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. That is useful for Service endpoint (A subnet should reach Azure Storage over Azure backbone with storage firewall scoped to that subnet). It does not meet the current Route Server dynamic routing requirement: A hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. Its design target is VNet peering. The stated requirement instead concerns: A hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn.
VPN Gateway can establish encrypted IPsec tunnels over public networks. It does not solve the specified Route Server dynamic routing condition.
The team has justified its SQL read scaling design with: Use supported SQL read scale-out replicas or a compatible reporting architecture. Which statement accurately describes why the approach works?
Read-only replicas can offload reporting from the primary where the tier provides the capability. It is material here because an online retailer has heavy read-only reporting queries that interfere with its primary transactional database.
Pooling reuses connections and reduces setup overhead relative to per-request creation. 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. Read-only replicas can offload reporting from the primary where the tier provides the capability.
Migration assessment identifies blockers and target-fit issues before a cutover. It belongs to SQL migration assessment. The stated architecture instead relies on: Read-only replicas can offload reporting from the primary where the tier provides the capability.
The design team completed work on Key Vault cryptographic signing. Its governing requirement was: An application must sign payloads with a centrally controlled key without exporting its private material. Identify the conclusive verification result.
Key Vault keys can perform cryptographic operations while restricting private key exposure. Confirm using the measurable result: The application receives a valid signature but cannot export the private key material.
Key Vault RBAC data permissions differ from vault resource-management permissions. The offered observation would demonstrate Vault RBAC least privilege: The user retrieves authorized secret values but cannot alter vault access configuration. The current validation is different: The application receives a valid signature but cannot export the private key material.
B2B collaboration supports guest principals and cross-organization access controls. Those observations validate External B2B partner. They do not establish the required Key Vault cryptographic signing result: The application receives a valid signature but cannot export the private key material.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The Resource lock constraints test checks authorized configuration updates succeed but the delete operation is blocked; the relevant outcome is The application receives a valid signature but cannot export the private key material.
During technical sign-off for VNet integration App Service, the architect selects: Use App Service regional VNet integration for outbound connectivity and private routing. Which underlying behavior should be documented?
VNet integration is principally an outbound feature; inbound private access requires other controls. It is material here because an App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests.
VNet peering alone is not transitive and forwarding needs explicit architecture. VNet integration is principally an outbound feature; inbound private access requires other controls.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. It belongs to Service endpoint. The stated architecture instead relies on: VNet integration is principally an outbound feature; inbound private access requires other controls.
Private endpoints provide a private inbound path for supported App Service access. VNet integration is principally an outbound feature; inbound private access requires other controls.
A rollout addressing Shared workload identity has reached acceptance testing. The original problem was: Two Functions apps need the same persistent workload identity even when one app is recreated. Which finding verifies its resolution?
A user-assigned identity has a lifecycle separate from each consuming Azure resource. Confirm using the measurable result: Both functions access the approved store and identity remains after one app is replaced.
Key Vault keys can perform cryptographic operations while restricting private key exposure. The distinguishing check is: Both functions access the approved store and identity remains after one app is replaced.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. The Key Vault certificate lifecycle test checks the renewed certificate is used by the endpoint before the old certificate expires; the relevant outcome is Both functions access the approved store and identity remains after one app is replaced.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. The offered observation would demonstrate Key Vault secrets: The service uses the new secret version without an embedded password in deployment artifacts. The current validation is different: Both functions access the approved store and identity remains after one app is replaced.
A TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes. Which Azure architecture would most directly achieve the required result: An unhealthy proxy node stops receiving new connections through the internal VIP?
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The selected architecture is use Azure Standard Internal Load Balancer with probes and backend pool; confirm the result by checking that an unhealthy proxy node stops receiving new connections through the internal VIP.
VPN Gateway can establish encrypted IPsec tunnels over public networks. It does not solve the specified Load Balancer internal L4 condition.
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. The relevant requirement is: A TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes.
VNet integration is principally an outbound feature; inbound private access requires other controls. That is useful for VNet integration App Service (An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests). It does not meet the current Load Balancer internal L4 requirement: A TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes.
The design team completed work on Hybrid route validation. Its governing requirement was: Migrated VMs can ping local peers but cannot access on-premises databases over ExpressRoute. Identify the conclusive verification result.
Hybrid reachability depends on both routing and security decisions in the destination VNet. Confirm using the measurable result: The Azure workload connects to on-prem data through the approved private network path.
Refactoring changes application structure and decouples independent workloads. The offered observation would demonstrate Refactor monolith: One service can scale independently and failures are isolated through messaging. The current validation is different: The Azure workload connects to on-prem data through the approved private network path.
Azure Migrate inventories servers and supports readiness and sizing assessments. Those observations validate Azure Migrate inventory. They do not establish the required Hybrid route validation result: The Azure workload connects to on-prem data through the approved private network path.
DNS cutover requires propagation and dependency planning independent of VM replication. The Networking cutover DNS test checks clients resolve the new endpoint and the rollback procedure returns traffic if needed; the relevant outcome is The Azure workload connects to on-prem data through the approved private network path.
Architecture rationale review—Premium SSD v2: Evaluate Premium SSD v2 managed disks where region and VM support permit. Which explanation accurately distinguishes this capability?
Premium SSD v2 decouples some provisioned performance settings from disk capacity. It is material here because a VM workload needs independently adjustable provisioned IOPS and throughput with SSD latency.
Immutable storage prevents overwrite and delete during the configured retention interval. Premium SSD v2 decouples some provisioned performance settings from disk capacity.
Cosmos DB provides a distributed document database with configurable consistency and throughput. That statement describes Cosmos DB NoSQL, while the question asks how Premium SSD v2 works: Premium SSD v2 decouples some provisioned performance settings from disk capacity.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. Premium SSD v2 decouples some provisioned performance settings from disk capacity.
Architecture review: Backup vault access and Vault immutability. Requirement A: Recovery operators need restore rights but should not be able to delete recovery services resources. Requirement B: A security audit worries a compromised backup administrator could delete protected recovery points. Which complete two-part proposal satisfies both constraints?
For requirement A, backup-specific RBAC roles separate operational restore tasks from vault administration. For requirement B, immutable backup settings can prevent specified destructive operations against protected backups. Verify both independently: A designated operator can restore an approved workload but cannot delete its vault; A forbidden backup deletion or retention reduction is rejected during the configured protection period.
One action is correct. The other targets Blob vaulted backup, leaving Vault immutability unsolved. Its necessary action is: Enable an appropriately configured immutable Azure Backup vault with supporting controls.
Backup-specific RBAC roles separate operational restore tasks from vault administration. Immutable backup settings can prevent specified destructive operations against protected backups. The proposed steps (use Azure Backup multi-user authorization with resource guard for protected operations; evaluate supported vaulted backup for blobs with documented feature and region limits) address other capabilities instead of this required pair.
The option covers one requirement but substitutes Multifactor critical operations for Backup vault access. The missing acceptance result is: A designated operator can restore an approved workload but cannot delete its vault.
Architecture review: SQL database PITR and SQL geo-restore. Requirement A: A deployment accidentally truncates a transaction table and the database must be recovered before the change. Requirement B: A SQL database without an active geo-secondary needs disaster recovery from geo-redundant backups. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure SQL automatic full differential and log backups support restoring database state at a selected time. For requirement B, geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. Verify both independently: A restored database contains transactions immediately preceding the truncation; A region-loss exercise recovers a database from the latest supported geo backup.
Azure SQL automatic full differential and log backups support restoring database state at a selected time. Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The proposed steps (assign scoped backup roles with least privilege and protected operation controls; evaluate continuous-backup mode if precise PITR is a firm requirement) address other capabilities instead of this required pair.
The first step implements Backup vault access instead of SQL database PITR. The necessary change is to use managed Azure SQL point-in-time restore to a new database within backup retention.
The option covers one requirement but substitutes Cosmos periodic backup for SQL geo-restore. The missing acceptance result is: A region-loss exercise recovers a database from the latest supported geo backup.
Please check your mailbox for a message from support@examlabs.com and follow the directions.