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 company wants shared analytics data products for Lakehouse and Warehouse consumers in one SaaS environment. Which Azure architecture would most directly achieve the required result: Authorized Fabric consumers query the shared curated data with governed access?
OneLake offers a common analytics data foundation for supported Fabric workloads. The selected architecture is evaluate Microsoft Fabric OneLake with suitable Lakehouse/Warehouse integration; confirm the result by checking that authorized Fabric consumers query the shared curated data with governed access.
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. Its design target is Azure Data Explorer telemetry. The stated requirement instead concerns: A company wants shared analytics data products for Lakehouse and Warehouse consumers in one SaaS environment.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. It does not solve the specified Fabric OneLake analytics condition.
Stream Analytics supports SQL-like processing over streaming sources with time windows. That is useful for Stream Analytics window (A telemetry stream needs five-minute event-time rolling aggregates without writing custom stream-processing code). It does not meet the current Fabric OneLake analytics requirement: A company wants shared analytics data products for Lakehouse and Warehouse consumers in one SaaS environment.
Architecture review: APIM rate limiting and API Management gateway. Requirement A: A popular API needs to reject excessive client requests without changing back-end services. Requirement B: Partners need one secured API entry point with subscription policies quotas and versioned back ends. Which complete two-part proposal satisfies both constraints?
For requirement A, APIM can enforce per-client API consumption controls before requests reach backends. For requirement B, APIM applies gateway policies authentication mediation throttling and API lifecycle controls. Verify both independently: A burst beyond the quota is throttled while permitted traffic proceeds; An expired subscription key fails while an authorized request routes to the correct version.
This combines Event Grid notification and Publish subscribe topics, which do not satisfy the distinct requirements for APIM rate limiting and API Management gateway.
The option covers one requirement but substitutes Event Grid notification for APIM rate limiting. The missing acceptance result is: A burst beyond the quota is throttled while permitted traffic proceeds.
One action is correct. The other targets Publish subscribe topics, leaving API Management gateway unsolved. Its necessary action is: Place Azure API Management in front of approved back-end APIs.
The VMSS dynamic scaling review proposes: Use Virtual Machine Scale Sets with metric-based autoscale and stateless instances. Which Azure behavior is the technical justification for this decision?
VMSS automates management and scaling of similar VMs in the same workload. It is material here because an autoscaling API needs several identical VMs during peak hours and only a few at night.
App Service manages web hosting and supports deployment slots on eligible plans. VMSS automates management and scaling of similar VMs in the same workload.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. That statement describes Azure Functions event, while the question asks how VMSS dynamic scaling works: VMSS automates management and scaling of similar VMs in the same workload.
Compute-optimized instances prioritize vCPU capacity over excess memory. VMSS automates management and scaling of similar VMs in the same workload.
A proposed solution for Role assignment scope is: Remove broad role inheritance and grant least-scope RBAC at the resource-group boundary. Select the strongest statement supporting the recommendation.
RBAC assignments inherit downward so narrower scope reduces unintended changes. It is material here because an engineer only operates one network resource group but has Contributor for the whole subscription.
Policy exemptions record approved exceptions while the policy remains assigned. It belongs to Policy exemption. The stated architecture instead relies on: RBAC assignments inherit downward so narrower scope reduces unintended changes.
Infrastructure as code declares desired resources and allows review and repeat deployment. That statement describes Standardized IaC, while the question asks how Role assignment scope works: RBAC assignments inherit downward so narrower scope reduces unintended changes.
Policy deny or audit effects can enforce required metadata at supported resource scopes. RBAC assignments inherit downward so narrower scope reduces unintended changes.
During technical sign-off for Resource group lifecycle, the architect selects: Group environment-owned resources into lifecycle-aligned resource groups. Which underlying behavior should be documented?
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. It is material here because short-lived environments must be removed together without deleting shared platform services.
Policy exemptions record approved exceptions while the policy remains assigned. That statement describes Policy exemption, while the question asks how Resource group lifecycle works: Resource groups provide a deployment and management boundary and facilitate cohesive cleanup.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. Resource groups provide a deployment and management boundary and facilitate cohesive cleanup.
Budgets monitor and notify about spending and do not automatically stop resources. It belongs to Cost budgets. The stated architecture instead relies on: Resource groups provide a deployment and management boundary and facilitate cohesive cleanup.
A proposed solution for Cosmos DB NoSQL is: Choose Azure Cosmos DB for NoSQL with suitable partition and consistency design. Select the strongest statement supporting the recommendation.
Cosmos DB provides a distributed document database with configurable consistency and throughput. It is material here because a globally distributed app stores schemaless JSON records at high scale with flexible document queries.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. Cosmos DB provides a distributed document database with configurable consistency and throughput.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. Cosmos DB provides a distributed document database with configurable consistency and throughput.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. That statement describes Blob HNS namespace, while the question asks how Cosmos DB NoSQL works: Cosmos DB provides a distributed document database with configurable consistency and throughput.
A rollout addressing Route Server dynamic routing has reached acceptance testing. The original problem was: A hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn. Which finding verifies its resolution?
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. Confirm using the measurable result: New approved NVA routes propagate to effective routes for attached workloads.
VNet integration is principally an outbound feature; inbound private access requires other controls. Those observations validate VNet integration App Service. They do not establish the required Route Server dynamic routing result: New approved NVA routes propagate to effective routes for attached workloads.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. The distinguishing check is: New approved NVA routes propagate to effective routes for attached workloads.
Private endpoints provide a private inbound path for supported App Service access. The Private inbound App Service test checks corporate users connect using private DNS and public clients are rejected; the relevant outcome is New approved NVA routes propagate to effective routes for attached workloads.
A solution must address both Confidential VM and Spot VM suitability. First requirement: A healthcare workload requires confidential computing protections during in-use processing. Second requirement: A rendering workload can checkpoint and tolerate eviction but has a tight compute budget. Select TWO recommendations that meet these independent needs.
For the Spot VM suitability half of this design, spot instances offer lower-priced spare capacity without guaranteed availability. Check: An eviction event restarts work from its last saved checkpoint on available capacity. The other half concerns Confidential VM.
For the Confidential VM half of this two-part design, confidential VMs use hardware-backed protection for sensitive guest execution environments. Verify: Guest attestation and encryption state meet the confidential VM policy. The other half concerns Spot VM suitability.
Dedicated Host provides physical host isolation with separate placement and pricing controls. That plan is appropriate for Dedicated host. The two controls sought here are Confidential VM and Spot VM suitability.
GPU instances provide accelerators not present on standard CPU-only VMs. Its own validation would be: The model uses available GPU memory and meets measured inference latency. The current paired requirement is Confidential VM and Spot VM suitability.
Azure Batch schedules large-scale parallel workloads across managed compute pools. The corresponding task is Azure Batch scheduling: Research jobs run thousands of independent parameter simulations and require queued pool-based compute. It is not one of the two requested controls (Confidential VM and Spot VM suitability).
A regulated subsidiary needs separate billing and policy boundaries from the parent business unit. An engineer must deliver the following acceptance evidence: The subsidiary's budget and policy reports stay distinct from the parent. What design choice is defensible?
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. The selected architecture is place regulated workloads in designated subscriptions under suitable management groups; confirm the result by checking that the subsidiary's budget and policy reports stay distinct from the parent.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Its design target is Resource naming governance. The stated requirement instead concerns: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit.
Infrastructure as code declares desired resources and allows review and repeat deployment. It does not solve the specified Subscription isolation condition.
Policy scope and exclusions should be the smallest feasible exception rather than removing global guardrails. That is useful for Policy exclusion scope (One application needs a carefully controlled exception to a management group policy). It does not meet the current Subscription isolation requirement: A regulated subsidiary needs separate billing and policy boundaries from the parent business unit.
A solution must address both MySQL managed service and PostgreSQL flexible server. First requirement: An existing MySQL application needs automated patching and backups with minimal database changes. Second requirement: An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM. Select TWO recommendations that meet these independent needs.
For the PostgreSQL flexible server half of this design, flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. Check: The required extension is available and the app connects without an OS-managed database host. The other half concerns MySQL managed service.
For the MySQL managed service half of this two-part design, flexible Server provides managed MySQL compute storage and backups. Verify: The application retains its MySQL driver and PITR test succeeds. The other half concerns PostgreSQL flexible server.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. The corresponding task is SQL Server on Azure VM: A database application depends on a third-party kernel-level driver installed alongside SQL Server. It is not one of the two requested controls (MySQL managed service and PostgreSQL flexible server).
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. That plan is appropriate for PostgreSQL read replica. The two controls sought here are MySQL managed service and PostgreSQL flexible server.
Migration assessment identifies blockers and target-fit issues before a cutover. This alternative solves SQL migration assessment, while the question separately requires MySQL managed service and PostgreSQL flexible server.
A rollout addressing Retry transient failures has reached acceptance testing. The original problem was: An application sends one request and crashes on transient 429 and 503 responses during scale events. Which finding verifies its resolution?
Transient-failure handling reduces unnecessary outages while preventing retry storms. Confirm using the measurable result: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. Those observations validate Front Door global failover. They do not establish the required Retry transient failures result: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Cluster autoscaler adjusts nodes to schedule eligible pending pods. The distinguishing check is: A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Traffic Manager is DNS-based and clients connect directly to the returned service endpoint. The Traffic Manager DNS routing test checks dNS responses prefer the healthy endpoint as monitoring marks another unavailable; the relevant outcome is A simulated 503 triggers spaced retries and a successful response without duplicate writes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.