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 rollout addressing VNet integration App Service has reached acceptance testing. The original problem was: An App Service must make outbound calls to a private SQL server while remaining publicly accessible for inbound requests. Which finding verifies its resolution?
VNet integration is principally an outbound feature; inbound private access requires other controls. Confirm using the measurable result: The app connects to private SQL via VNet while its public frontend remains reachable as intended.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. Those observations validate Service endpoint. They do not establish the required VNet integration App Service result: The app connects to private SQL via VNet while its public frontend remains reachable as intended.
VNet peering alone is not transitive and forwarding needs explicit architecture. The distinguishing check is: The app connects to private SQL via VNet while its public frontend remains reachable as intended.
Private endpoints provide a private inbound path for supported App Service access. The offered observation would demonstrate Private inbound App Service: Corporate users connect using private DNS and public clients are rejected. The current validation is different: The app connects to private SQL via VNet while its public frontend remains reachable as intended.
An architect must sign off on Policy audit versus deny. The business problem is: The platform team needs to measure the impact of a new restriction before blocking deployments. What observed test result provides valid evidence?
Audit effects collect compliance findings without blocking resource creation. Confirm using the measurable result: Noncompliant deployment is logged during pilot but rejected after approved enforcement.
Initiatives bundle related policy rules and support shared compliance reporting. The distinguishing check is: Noncompliant deployment is logged during pilot but rejected after approved enforcement.
Budgets monitor and notify about spending and do not automatically stop resources. The offered observation would demonstrate Cost budgets: A threshold crossing issues notifications while the app remains running. The current validation is different: Noncompliant deployment is logged during pilot but rejected after approved enforcement.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. Those observations validate Resource naming governance. They do not establish the required Policy audit versus deny result: Noncompliant deployment is logged during pilot but rejected after approved enforcement.
Architecture review: Load Balancer internal L4 and Application Gateway internal. Requirement A: A TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes. Requirement B: An internal web app needs URL path routing and WAF-like inspection behind a private frontend. Which complete two-part proposal satisfies both constraints?
For requirement A, Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. For requirement B, application Gateway provides regional Layer 7 reverse proxy and routing for private backends. Verify both independently: An unhealthy proxy node stops receiving new connections through the internal VIP; Internal clients reach /api and /web paths through the private gateway and external clients cannot.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. The proposed steps (deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings; use VNet peering or global VNet peering under the supported region topology) address other capabilities instead of this required pair.
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. The other proposed action (use VNet peering or global VNet peering under the supported region topology) addresses a different operation. Application Gateway provides regional Layer 7 reverse proxy and routing for private backends.
One action is correct. The other targets Site-to-site VPN, leaving Load Balancer internal L4 unsolved. Its necessary action is: Use Azure Standard Internal Load Balancer with probes and backend pool.
Before approving AKS cluster autoscaler, the reviewer assesses this requirement: Node pool capacity becomes insufficient for pending pods during daily traffic peaks. Which of the reported outcomes is decisive?
Cluster autoscaler adjusts nodes to schedule eligible pending pods. Confirm using the measurable result: Pending pods move to new nodes before the measured capacity deadline.
A zone-separated standby supports automated failover where offered. The offered observation would demonstrate PostgreSQL zone redundant HA: After a zone failure the managed standby serves database connections. The current validation is different: Pending pods move to new nodes before the measured capacity deadline.
Availability zones isolate infrastructure failure domains within an enabled region. Those observations validate Availability zones for VM tier. They do not establish the required AKS cluster autoscaler result: Pending pods move to new nodes before the measured capacity deadline.
Graceful scale-in lets existing requests finish while the removed instance stops taking new traffic. The Graceful scale-in test checks the scale-in test completes active requests while newly arriving calls use surviving workers; the relevant outcome is Pending pods move to new nodes before the measured capacity deadline.
The Migration landing zone review proposes: Create an Azure landing zone before migration waves using CAF guidance. Which Azure behavior is the technical justification for this decision?
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. It is material here because a program plans 100 app moves but lacks identity, DNS, governance and network foundations.
PostgreSQL migration requires extension, version and connectivity compatibility checks. Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads.
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 Migration landing zone works: Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads.
Object count alone cannot establish content integrity or ACL preservation. Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads.
An application must sign payloads with a centrally controlled key without exporting its private material. Choose the architecture that can be validated by this result: The application receives a valid signature but cannot export the private key material.
Key Vault keys can perform cryptographic operations while restricting private key exposure. The selected architecture is use Azure Key Vault key operations with a suitable key type and access permissions; confirm the result by checking that the application receives a valid signature but cannot export the private key material.
B2B collaboration supports guest principals and cross-organization access controls. It does not solve the specified Key Vault cryptographic signing condition.
Key Vault RBAC data permissions differ from vault resource-management permissions. The relevant requirement is: An application must sign payloads with a centrally controlled key without exporting its private material.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The current need is: An application must sign payloads with a centrally controlled key without exporting its private material.
The target environment adopts this approach for Confidential VM: Choose eligible Azure confidential VMs with supported confidential-computing features. What property makes it suitable?
Confidential VMs use hardware-backed protection for sensitive guest execution environments. It is material here because a healthcare workload requires confidential computing protections during in-use processing.
VMSS automates management and scaling of similar VMs in the same workload. That statement describes VMSS dynamic scaling, while the question asks how Confidential VM works: Confidential VMs use hardware-backed protection for sensitive guest execution environments.
Blue-green deployment preserves a prior known-good instance while testing a replacement. Confidential VMs use hardware-backed protection for sensitive guest execution environments.
General-purpose VMs balance CPU and memory while retaining OS-level control. It belongs to General purpose VM. The stated architecture instead relies on: Confidential VMs use hardware-backed protection for sensitive guest execution environments.
The acceptance criterion for Replatform database comes from this issue: A SQL application can move to managed SQL with a few configuration changes but needs no redesign. Which measured outcome is the strongest proof?
Replatforming changes hosting characteristics while preserving most app behavior. Confirm using the measurable result: Migration validation shows required database features function on the selected managed tier.
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: Migration validation shows required database features function on the selected managed tier.
Object count alone cannot establish content integrity or ACL preservation. The distinguishing check is: Migration validation shows required database features function on the selected managed tier.
Physical data transfer can shorten initial bulk migration when network transfer is impractical. The Storage bulk offline transfer test checks the imported objects reconcile against checksums and manifests; the relevant outcome is Migration validation shows required database features function on the selected managed tier.
A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. The acceptance test is: A denied deployment and a successful resource deletion appear with caller and operation name. Which design recommendation best satisfies both?
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The selected architecture is route Azure Activity Log to a central Log Analytics workspace through diagnostic settings; confirm the result by checking that a denied deployment and a successful resource deletion appear with caller and operation name.
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The current need is: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. That is useful for Cross-subscription workspace (Four subscriptions must be searched together during incident response with one KQL query and shared retention policy). It does not meet the current Control-plane audit requirement: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs.
DeployIfNotExists can evaluate related configurations and deploy missing compliant resources with appropriate permissions. It does not solve the specified Control-plane audit condition.
During technical sign-off for Spot VM suitability, the architect selects: Use Azure Spot VMs with checkpointing and capacity-aware fallback. Which underlying behavior should be documented?
Spot instances offer lower-priced spare capacity without guaranteed availability. It is material here because a rendering workload can checkpoint and tolerate eviction but has a tight compute budget.
ASE provides dedicated App Service hosting in a customer virtual-network environment. It belongs to App Service isolation. The stated architecture instead relies on: Spot instances offer lower-priced spare capacity without guaranteed availability.
HPC workloads require specialized low-latency fabric support beyond commodity VMs. Spot instances offer lower-priced spare capacity without guaranteed availability.
GPU instances provide accelerators not present on standard CPU-only VMs. Spot instances offer lower-priced spare capacity without guaranteed availability.
A proposed solution for Cross-subscription workspace is: Send supported resource logs from each subscription into a centralized Log Analytics workspace. Select the strongest statement supporting the recommendation.
A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured. It is material here because four subscriptions must be searched together during incident response with one KQL query and shared retention policy.
WAF rule and access diagnostics identify rule IDs and request outcomes that aggregate health metrics miss. That statement describes WAF decision logs, while the question asks how Cross-subscription workspace works: A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. It belongs to Network-flow telemetry. The stated architecture instead relies on: A workspace can aggregate resource telemetry across subscription boundaries when access and diagnostic routing are configured.
Please check your mailbox for a message from support@examlabs.com and follow the directions.