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 acceptance criterion for SQL compute scaling comes from this issue: A database must grow compute during a seasonal sales period but not during idle months. Which measured outcome is the strongest proof?
Managed SQL compute tiers can scale resources but scaling may have operational consequences. Confirm using the measurable result: A scheduled scale-up meets throughput and a later scale-down reduces cost.
Read-only replicas can offload reporting from the primary where the tier provides the capability. The SQL read scaling test checks reporting connections route to a readable replica while transactions remain on primary; the relevant outcome is A scheduled scale-up meets throughput and a later scale-down reduces cost.
Hyperscale decouples storage scale from compute and supports large database sizes. The offered observation would demonstrate SQL Hyperscale growth: A growth test reaches the required storage target with the expected compute and backup architecture. The current validation is different: A scheduled scale-up meets throughput and a later scale-down reduces cost.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. Those observations validate SQL database partitioning. They do not establish the required SQL compute scaling result: A scheduled scale-up meets throughput and a later scale-down reduces cost.
The team has justified its Azure SQL Database single database design with: Select Azure SQL Database for the managed individual database. Which statement accurately describes why the approach works?
Azure SQL Database offers fully managed relational database operations with automated backups. It is material here because a SaaS app runs a standalone transactional SQL Server-compatible database and must avoid managing operating systems.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. Azure SQL Database offers fully managed relational database operations with automated backups.
Serverless compute can scale usage and pause eligible databases to reduce idle cost. Azure SQL Database offers fully managed relational database operations with automated backups.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. That statement describes SQL Server on Azure VM, while the question asks how Azure SQL Database single database works: Azure SQL Database offers fully managed relational database operations with automated backups.
An architect must sign off on Front Door WAF edge. The business problem is: A public application must block common HTTP attacks before traffic reaches regional origins worldwide. What observed test result provides valid evidence?
Edge WAF can inspect and filter HTTP requests before the proxy forwards them to origins. Confirm using the measurable result: A permitted request reaches its origin while a malicious test pattern is blocked at the edge.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. The distinguishing check is: A permitted request reaches its origin while a malicious test pattern is blocked at the edge.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. The Virtual WAN global hubs test checks a branch reaches authorized remote VNets through the intended virtual hub routes; the relevant outcome is A permitted request reaches its origin while a malicious test pattern is blocked at the edge.
VNet integration is principally an outbound feature; inbound private access requires other controls. The offered observation would demonstrate VNet integration App Service: The app connects to private SQL via VNet while its public frontend remains reachable as intended. The current validation is different: A permitted request reaches its origin while a malicious test pattern is blocked at the edge.
The General purpose VM review proposes: Choose an appropriately sized general-purpose Azure VM with supporting disks and network. Which Azure behavior is the technical justification for this decision?
General-purpose VMs balance CPU and memory while retaining OS-level control. It is material here because a legacy Windows service requires full OS control and custom drivers but has moderate CPU and memory needs.
Spot instances offer lower-priced spare capacity without guaranteed availability. It belongs to Spot VM suitability. The stated architecture instead relies on: General-purpose VMs balance CPU and memory while retaining OS-level control.
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. General-purpose VMs balance CPU and memory while retaining OS-level control.
ACR stores OCI images and supports Azure identity-based authorization to the registry. General-purpose VMs balance CPU and memory while retaining OS-level control.
Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable. Identify the most suitable implementation for an outcome where a test failover can reach the recovered app through the intended private routes.
Compute replication does not automatically guarantee complete application network reachability. The selected architecture is plan ASR recovery VNet, IP addressing, NSGs, routing and DNS before failover; confirm the result by checking that a test failover can reach the recovered app through the intended private routes.
Azure Backup creates managed recovery points distinct from continuously replicating a running VM. The relevant requirement is: Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable.
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. The current need is: Replicated VMs boot in the secondary region but application private DNS and subnets are unavailable.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. It does not solve the specified Azure-to-Azure ASR networking condition.
Architecture review: Consumer sign-in and External B2B partner. Requirement A: An external-facing consumer application requires local and social identity sign-in separate from workforce identities. Requirement B: A supplier must access a specific application without becoming an employee in the home tenant. Which complete two-part proposal satisfies both constraints?
For requirement A, external ID consumer capabilities support customer journeys distinct from employee workforce governance. For requirement B, b2B collaboration supports guest principals and cross-organization access controls. Verify both independently: The consumer completes the intended registration journey without receiving workforce resource roles; The supplier opens the assigned application but cannot access unrelated tenant resources.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. The other proposed action (use secure parameter references and retrieve protected values from an approved secret store) addresses a different operation. B2B collaboration supports guest principals and cross-organization access controls.
Both proposed halves address other use cases: Resource lock constraints and Secrets in deployment pipeline. The requested pair is Consumer sign-in and External B2B partner.
One action is correct. The other targets Resource lock constraints, leaving Consumer sign-in unsolved. Its necessary action is: Use an appropriate Microsoft Entra External ID customer identity design.
Architecture rationale review—Security-event streaming: Route supported platform diagnostic events to an Event Hubs namespace. Which explanation accurately distinguishes this capability?
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. It is material here because the SOC streams resource events into an external SIEM and needs independent replay and consumer handling.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. Event Hubs provides durable high-throughput event ingestion for downstream stream consumers.
Action groups define notifications and automated responses and can be reused by alert rules. It belongs to Notification routing. The stated architecture instead relies on: Event Hubs provides durable high-throughput event ingestion for downstream stream consumers.
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. That statement describes Synthetic uptime, while the question asks how Security-event streaming works: Event Hubs provides durable high-throughput event ingestion for downstream stream consumers.
Architecture rationale review—AKS cluster autoscaler: Enable AKS cluster autoscaler within approved node pool bounds. Which explanation accurately distinguishes this capability?
Cluster autoscaler adjusts nodes to schedule eligible pending pods. It is material here because node pool capacity becomes insufficient for pending pods during daily traffic peaks.
A zone-separated standby supports automated failover where offered. It belongs to PostgreSQL zone redundant HA. The stated architecture instead relies on: Cluster autoscaler adjusts nodes to schedule eligible pending pods.
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. That statement describes Graceful scale-in, while the question asks how AKS cluster autoscaler works: Cluster autoscaler adjusts nodes to schedule eligible pending pods.
Availability zones isolate infrastructure failure domains within an enabled region. Cluster autoscaler adjusts nodes to schedule eligible pending pods.
For the SQL migration assessment requirement, the proposed architecture uses: Run Azure SQL migration assessment and remediate feature compatibility findings. Why does that design fit?
Migration assessment identifies blockers and target-fit issues before a cutover. It is material here because a legacy SQL database contains unsupported features and the team wants a target tier before moving.
Temporal tables retain row history and support as-of queries independently of whole-database backups. That statement describes SQL temporal tables, while the question asks how SQL migration assessment works: Migration assessment identifies blockers and target-fit issues before a cutover.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. Migration assessment identifies blockers and target-fit issues before a cutover.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. It belongs to PostgreSQL read replica. The stated architecture instead relies on: Migration assessment identifies blockers and target-fit issues before a cutover.
A supplier must access a specific application without becoming an employee in the home tenant. A deployment must satisfy this operational criterion: The supplier opens the assigned application but cannot access unrelated tenant resources. Which plan is appropriate?
B2B collaboration supports guest principals and cross-organization access controls. The selected architecture is use Microsoft Entra B2B collaboration with scoped application access and appropriate external identities policy; confirm the result by checking that the supplier opens the assigned application but cannot access unrelated tenant resources.
Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. The relevant requirement is: A supplier must access a specific application without becoming an employee in the home tenant.
Managed identities provide Entra tokens to supported workloads while data-plane RBAC grants the actual blob permissions. The current need is: A supplier must access a specific application without becoming an employee in the home tenant.
Secure secret handling removes reusable credentials from source while preserving automation. It does not solve the specified External B2B partner condition.
The design team completed work on Memory optimized VM. Its governing requirement was: An in-memory analytics engine repeatedly pages memory on a standard VM size. Identify the conclusive verification result.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. Confirm using the measurable result: Paging falls and the working data fits within the selected RAM capacity.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. Those observations validate Autoscaling based on queue. They do not establish the required Memory optimized VM result: Paging falls and the working data fits within the selected RAM capacity.
Compute Gallery distributes managed image versions for repeatable VM deployments. The distinguishing check is: Paging falls and the working data fits within the selected RAM capacity.
ASE provides dedicated App Service hosting in a customer virtual-network environment. The App Service isolation test checks the app operates in the required isolated hosting boundary and passes private connectivity tests; the relevant outcome is Paging falls and the working data fits within the selected RAM capacity.
Please check your mailbox for a message from support@examlabs.com and follow the directions.