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
The Hub-spoke topology review proposes: Use a hub-and-spoke network topology with shared service governance. Which Azure behavior is the technical justification for this decision?
A hub centralizes connectivity services while spoke VNets isolate applications. It is material here because many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway.
VNet peering alone is not transitive and forwarding needs explicit architecture. It belongs to Peering nontransitivity. The stated architecture instead relies on: A hub centralizes connectivity services while spoke VNets isolate applications.
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. That statement describes UDR firewall inspection, while the question asks how Hub-spoke topology works: A hub centralizes connectivity services while spoke VNets isolate applications.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. A hub centralizes connectivity services while spoke VNets isolate applications.
Architecture review: Network Watcher diagnosis and NSG subnet filtering. Requirement A: A connectivity failure may be caused by either NSG rules, routing or the remote endpoint. Requirement B: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall. Which complete two-part proposal satisfies both constraints?
For requirement A, network Watcher diagnostic tools identify effective network behavior and filtering decisions. For requirement B, nSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Verify both independently: The test identifies the blocking NSG rule or unreachable next hop before changing production routes; The approved source reaches TCP 443 and another source is denied.
One action is correct. The other targets DDoS protection, leaving NSG subnet filtering unsolved. Its necessary action is: Apply NSG rules at an appropriate subnet or NIC scope.
This combines Service endpoint and DDoS protection, which do not satisfy the distinct requirements for Network Watcher diagnosis and NSG subnet filtering.
The option covers one requirement but substitutes Service endpoint for Network Watcher diagnosis. The missing acceptance result is: The test identifies the blocking NSG rule or unreachable next hop before changing production routes.
The SQL database partitioning review proposes: Design appropriate table partitioning and indexing for workload query patterns. Which Azure behavior is the technical justification for this decision?
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. It is material here because a large transaction table suffers scans on historical data and needs time-based management.
Migration assessment identifies blockers and target-fit issues before a cutover. Partition elimination and aligned indexes can reduce scans when predicates match partition keys.
Temporal tables retain row history and support as-of queries independently of whole-database backups. Partition elimination and aligned indexes can reduce scans when predicates match partition keys.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. It belongs to SQL database monitoring. The stated architecture instead relies on: Partition elimination and aligned indexes can reduce scans when predicates match partition keys.
Architecture review: Azure Functions durable workflow and VMSS dynamic scaling. Requirement A: A workflow waits hours between steps while retaining orchestration state through restarts. Requirement B: An autoscaling API needs several identical VMs during peak hours and only a few at night. Which complete two-part proposal satisfies both constraints?
For requirement A, durable Functions manages stateful workflows over serverless function executions. For requirement B, VMSS automates management and scaling of similar VMs in the same workload. Verify both independently: A resumed orchestration continues from saved state after a worker restart; The scale set adds instances at load and returns to baseline under low demand.
The option covers one requirement but substitutes Azure Batch scheduling for Azure Functions durable workflow. The missing acceptance result is: A resumed orchestration continues from saved state after a worker restart.
One action is correct. The other targets App Service web, leaving VMSS dynamic scaling unsolved. Its necessary action is: Use Virtual Machine Scale Sets with metric-based autoscale and stateless instances.
Durable Functions manages stateful workflows over serverless function executions. VMSS automates management and scaling of similar VMs in the same workload. The proposed steps (use Azure Batch pools, tasks and job orchestration; choose Azure App Service on a suitable tier with deployment slots) address other capabilities instead of this required pair.
For the Azure File Sync requirement, the proposed architecture uses: Use Azure File Sync with suitable cloud tiering and server endpoints. Why does that design fit?
File Sync preserves local namespace access while synchronizing with Azure file shares. It is material here because a branch file server should retain local caching while most data moves to Azure Files.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. File Sync preserves local namespace access while synchronizing with Azure file shares.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. That statement describes Physical server migration, while the question asks how Azure File Sync works: File Sync preserves local namespace access while synchronizing with Azure file shares.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. File Sync preserves local namespace access while synchronizing with Azure file shares.
A developer deletes Cosmos DB documents and needs to restore the account to an earlier instant. An architecture board will approve a solution only if this outcome is demonstrated: A restored account contains the pre-deletion documents at the chosen restore timestamp. What should be selected?
Continuous backup can support point-in-time restore for supported Cosmos API accounts. The selected architecture is use Cosmos DB continuous backup mode with appropriate restore capabilities; confirm the result by checking that a restored account contains the pre-deletion documents at the chosen restore timestamp.
Multi-user authorization separates approval boundaries for critical backup changes. Its design target is Multifactor critical operations. The stated requirement instead concerns: A developer deletes Cosmos DB documents and needs to restore the account to an earlier instant.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. The relevant requirement is: A developer deletes Cosmos DB documents and needs to restore the account to an earlier instant.
Backup-specific RBAC roles separate operational restore tasks from vault administration. It does not solve the specified Cosmos continuous backup condition.
The team has justified its Log anomaly alert design with: Create a scheduled log-search alert that evaluates a KQL query and threshold. Which statement accurately describes why the approach works?
A log search alert can evaluate aggregated matching records instead of only raw metric time series. It is material here because security needs an alert when failed sign-in counts by IP exceed a KQL-defined rule over fifteen minutes.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. A log search alert can evaluate aggregated matching records instead of only raw metric time series.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. A log search alert can evaluate aggregated matching records instead of only raw metric time series.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. It belongs to Web transaction traces. The stated architecture instead relies on: A log search alert can evaluate aggregated matching records instead of only raw metric time series.
Architecture review: Cosmos session consistency and Cosmos autoscale. Requirement A: A customer portal must read its own updates while accepting that other users may briefly see stale writes. Requirement B: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful. Which complete two-part proposal satisfies both constraints?
For requirement A, session consistency offers read-your-writes within a session without strong global consistency. For requirement B, autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. Verify both independently: The writing session immediately reads its own update while other sessions may lag; Busy-hour requests meet RU demands and off-peak consumed RU declines.
The option covers one requirement but substitutes Blob immutability for Cosmos session consistency. The missing acceptance result is: The writing session immediately reads its own update while other sessions may lag.
Session consistency offers read-your-writes within a session without strong global consistency. Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The proposed steps (configure compliant immutable blob retention policies at supported scope; configure Azure Storage Blob Inventory reports) address other capabilities instead of this required pair.
The mismatched half is Blob inventory; Cosmos autoscale instead needs: Use Cosmos DB autoscale throughput within tested RU limits.
A solution must address both NSG subnet filtering and Service endpoint. First requirement: A team must restrict a VM subnet to TCP 443 from a management prefix without deploying a full firewall. Second requirement: A subnet should reach Azure Storage over Azure backbone with storage firewall scoped to that subnet. Select TWO recommendations that meet these independent needs.
For the NSG subnet filtering half of this two-part design, nSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Verify: The approved source reaches TCP 443 and another source is denied. The other half concerns Service endpoint.
For the Service endpoint half of this design, service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. Check: The approved subnet accesses storage and unauthorized internet clients are blocked. The other half concerns NSG subnet filtering.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. The corresponding task is Application Gateway internal: An internal web app needs URL path routing and WAF-like inspection behind a private frontend. It is not one of the two requested controls (NSG subnet filtering and Service endpoint).
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 NSG subnet filtering and Service endpoint.
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. The corresponding task is Front Door WAF edge: A public application must block common HTTP attacks before traffic reaches regional origins worldwide. It is not one of the two requested controls (NSG subnet filtering and Service endpoint).
The target environment adopts this approach for SQL Hyperscale growth: Evaluate Azure SQL Database Hyperscale with applicable workload support. What property makes it suitable?
Hyperscale decouples storage scale from compute and supports large database sizes. It is material here because one operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. It belongs to SQL managed instance compatibility. The stated architecture instead relies on: Hyperscale decouples storage scale from compute and supports large database sizes.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Hyperscale decouples storage scale from compute and supports large database sizes.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. Hyperscale decouples storage scale from compute and supports large database sizes.
During technical sign-off for Recovery point objective, the architect selects: Use a replication and write-consistency design verified against the five-minute RPO. Which underlying behavior should be documented?
RPO measures the maximum tolerated data loss period at a recovery point. It is material here because a business may lose at most five minutes of writes during failover.
Immutable backup settings can prevent specified destructive operations against protected backups. That statement describes Vault immutability, while the question asks how Recovery point objective works: RPO measures the maximum tolerated data loss period at a recovery point.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. RPO measures the maximum tolerated data loss period at a recovery point.
Managed PostgreSQL backups support rebuilding a server at a selected valid recovery time. It belongs to PostgreSQL PITR. The stated architecture instead relies on: RPO measures the maximum tolerated data loss period at a recovery point.
Please check your mailbox for a message from support@examlabs.com and follow the directions.