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 design team completed work on Identity-signin monitoring. Its governing requirement was: Security analysts require long-term sign-in analysis alongside cloud resource diagnostics. Identify the conclusive verification result.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. Confirm using the measurable result: Risky sign-ins can be queried with resource access events over the chosen time window.
VM insights and the agent collect supported guest operating-system counters and process data. The VM guest performance test checks per-VM guest memory and disk metrics appear with host identity in Azure Monitor; the relevant outcome is Risky sign-ins can be queried with resource access events over the chosen time window.
Application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. The offered observation would demonstrate Web transaction traces: A failed transaction trace identifies its failing dependency and correlated exception. The current validation is different: Risky sign-ins can be queried with resource access events over the chosen time window.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. Those observations validate Control-plane audit. They do not establish the required Identity-signin monitoring result: Risky sign-ins can be queried with resource access events over the chosen time window.
A payment system must resume in thirty minutes after a regional outage. An engineer must deliver the following acceptance evidence: A regional failover test restores business service in less than the allowed interval. What design choice is defensible?
RTO is the maximum acceptable restoration duration, not the amount of lost data. The selected architecture is choose a standby and failover design measured against the thirty-minute RTO; confirm the result by checking that a regional failover test restores business service in less than the allowed interval.
Backup-specific RBAC roles separate operational restore tasks from vault administration. The relevant requirement is: A payment system must resume in thirty minutes after a regional outage.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. It does not solve the specified Recovery time objective condition.
Immutable backup settings can prevent specified destructive operations against protected backups. That is useful for Vault immutability (A security audit worries a compromised backup administrator could delete protected recovery points). It does not meet the current Recovery time objective requirement: A payment system must resume in thirty minutes after a regional outage.
To validate the SQL Hyperscale growth deployment, reviewers revisit this operational need: One operational SQL database must scale beyond the capacity limits of ordinary General Purpose storage tiers. What result confirms it was met?
Hyperscale decouples storage scale from compute and supports large database sizes. Confirm using the measurable result: A growth test reaches the required storage target with the expected compute and backup architecture.
IaaS retains operating-system and SQL instance control that PaaS databases do not provide. Those observations validate SQL Server on Azure VM. They do not establish the required SQL Hyperscale growth result: A growth test reaches the required storage target with the expected compute and backup architecture.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. The distinguishing check is: A growth test reaches the required storage target with the expected compute and backup architecture.
Managed Instance supports many instance-scoped SQL Server capabilities with a managed service. The SQL managed instance compatibility test checks compatibility assessment and agent-dependent workloads complete without rewriting required instance features; the relevant outcome is A growth test reaches the required storage target with the expected compute and backup architecture.
The acceptance criterion for App Service isolation comes from this issue: A regulated web application needs private dedicated hosting and stricter network isolation. Which measured outcome is the strongest proof?
ASE provides dedicated App Service hosting in a customer virtual-network environment. Confirm using the measurable result: The app operates in the required isolated hosting boundary and passes private connectivity tests.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. The distinguishing check is: The app operates in the required isolated hosting boundary and passes private connectivity tests.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. The offered observation would demonstrate Autoscaling based on queue: The number of workers grows with queue backlog and contracts after processing. The current validation is different: The app operates in the required isolated hosting boundary and passes private connectivity tests.
General-purpose VMs balance CPU and memory while retaining OS-level control. Those observations validate General purpose VM. They do not establish the required App Service isolation result: The app operates in the required isolated hosting boundary and passes private connectivity tests.
An online retailer has heavy read-only reporting queries that interfere with its primary transactional database. Which Azure architecture would most directly achieve the required result: Reporting connections route to a readable replica while transactions remain on primary?
Read-only replicas can offload reporting from the primary where the tier provides the capability. The selected architecture is use supported SQL read scale-out replicas or a compatible reporting architecture; confirm the result by checking that reporting connections route to a readable replica while transactions remain on primary.
Query and resource telemetry helps distinguish costly queries from insufficient database compute. It does not solve the specified SQL read scaling condition.
CMK encryption protects database data at rest while keys are managed under customer control. The current need is: An online retailer has heavy read-only reporting queries that interfere with its primary transactional database.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. That is useful for SQL schema isolation (A multitenant app needs strong tenant-level database isolation and easy tenant backup/restore). It does not meet the current SQL read scaling requirement: An online retailer has heavy read-only reporting queries that interfere with its primary transactional database.
A scheduled daemon must call Microsoft Graph without an interactive user session. A deployment must satisfy this operational criterion: The service obtains an app-only token and performs only the approved Graph actions. Which plan is appropriate?
App-only permissions grant service principal operations without a delegated signed-in user. The selected architecture is use application permissions with admin consent and an appropriate confidential credential or federation; confirm the result by checking that the service obtains an app-only token and performs only the approved Graph actions.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The current need is: A scheduled daemon must call Microsoft Graph without an interactive user session.
B2B collaboration supports guest principals and cross-organization access controls. It does not solve the specified Application permissions condition.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Its design target is Key Vault secrets. The stated requirement instead concerns: A scheduled daemon must call Microsoft Graph without an interactive user session.
An IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control. Which Azure architecture would most directly achieve the required result: The committed deployment files contain no functional credentials and the deployment still succeeds?
Secure secret handling removes reusable credentials from source while preserving automation. The selected architecture is use secure parameter references and retrieve protected values from an approved secret store; confirm the result by checking that the committed deployment files contain no functional credentials and the deployment still succeeds.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. It does not solve the specified Secrets in deployment pipeline condition.
Delegated permissions represent what an application can do on behalf of an authenticated user. Its design target is App registration API scopes. The stated requirement instead concerns: An IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control.
App-only permissions grant service principal operations without a delegated signed-in user. The relevant requirement is: An IaC deployment includes a storage connection string directly in ARM/Bicep parameter files committed to source control.
During technical sign-off for Application Gateway zone redundancy, the architect selects: Use a supported zone-redundant Application Gateway WAF tier. Which underlying behavior should be documented?
Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer. It is material here because a web workload requires HTTP routing and WAF across availability zones.
Transient-failure handling reduces unnecessary outages while preventing retry storms. It belongs to Retry transient failures. The stated architecture instead relies on: Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer.
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. That statement describes AKS pod disruption budget, while the question asks how Application Gateway zone redundancy works: Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer.
Fault injection tests whether resilience patterns work under realistic failure conditions. Application Gateway offers L7 proxy capabilities with WAF unlike a basic L4 load balancer.
A rollout addressing Resource group lifecycle has reached acceptance testing. The original problem was: Short-lived environments must be removed together without deleting shared platform services. Which finding verifies its resolution?
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. Confirm using the measurable result: Deleting an approved test resource group removes only the intended environment resources.
Azure service quotas are often scoped by subscription and region and can constrain deployability. The offered observation would demonstrate Quotas and limits: A capacity forecast and quota decision support the planned deployment without surprise allocation errors. The current validation is different: Deleting an approved test resource group removes only the intended environment resources.
Audit effects collect compliance findings without blocking resource creation. Those observations validate Policy audit versus deny. They do not establish the required Resource group lifecycle result: Deleting an approved test resource group removes only the intended environment resources.
Cost exports provide detailed recurring usage data for downstream allocation reporting. The distinguishing check is: Deleting an approved test resource group removes only the intended environment resources.
A proposed solution for Azure Site Recovery failover is: Design Azure Site Recovery replication and recovery plans with test failover. Select the strongest statement supporting the recommendation.
Site Recovery replicates workload state and orchestrates VM failover for supported scenarios. It is material here because an enterprise VM workload needs a tested recovery-site boot process after complete primary-region loss.
LTR retains selected full backups over years rather than only the standard short PITR window. Site Recovery replicates workload state and orchestrates VM failover for supported scenarios.
Vaulted blob backup supplies protected backup storage with different capabilities than operational backups. Site Recovery replicates workload state and orchestrates VM failover for supported scenarios.
Backup-specific RBAC roles separate operational restore tasks from vault administration. That statement describes Backup vault access, while the question asks how Azure Site Recovery failover works: Site Recovery replicates workload state and orchestrates VM failover for supported scenarios.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.