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 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.
The SQL online migration review proposes: Use a supported online migration approach with initial load and continuous changes. Which Azure behavior is the technical justification for this decision?
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. It is material here because a high-volume database allows little cutover downtime and must synchronize changes before switch.
AzCopy provides scripted high-throughput online transfers with resumability. Online migration reduces cutover downtime by applying ongoing changes after the baseline copy.
Parallel operation compares business outputs before committing the cutover. It belongs to Parallel-run cutover. The stated architecture instead relies on: Online migration reduces cutover downtime by applying ongoing changes after the baseline copy.
Hidden dependencies can break after migration even when VM replication succeeds. That statement describes Application dependency mapping, while the question asks how SQL online migration works: Online migration reduces cutover downtime by applying ongoing changes after the baseline copy.
The target environment adopts this approach for Resource lock constraints: Add an appropriate CanNotDelete lock while maintaining suitable RBAC permissions. What property makes it suitable?
Management locks guard against accidental resource deletes and operate separately from authorization roles. It is material here because an application owner accidentally deletes resources but granting Reader would block legitimate configuration changes.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Management locks guard against accidental resource deletes and operate separately from authorization roles.
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. That statement describes Workload identity federation, while the question asks how Resource lock constraints works: Management locks guard against accidental resource deletes and operate separately from authorization roles.
External ID consumer capabilities support customer journeys distinct from employee workforce governance. Management locks guard against accidental resource deletes and operate separately from authorization roles.
Several HTTP container services need autoscaling and revisions without management of a full Kubernetes control plane. A deployment must satisfy this operational criterion: A new revision handles traffic and scales down when request demand is low. Which plan is appropriate?
Container Apps provides managed container hosting and microservice scale with KEDA capabilities. The selected architecture is use Azure Container Apps with suitable ingress scaling and revision settings; confirm the result by checking that a new revision handles traffic and scales down when request demand is low.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. Its design target is Azure Functions event. The stated requirement instead concerns: Several HTTP container services need autoscaling and revisions without management of a full Kubernetes control plane.
Encryption sets connect managed disk encryption to customer-owned keys. It does not solve the specified Container Apps microservice condition.
Blue-green deployment preserves a prior known-good instance while testing a replacement. The current need is: Several HTTP container services need autoscaling and revisions without management of a full Kubernetes control plane.
A rollout addressing Event Grid notification has reached acceptance testing. The original problem was: A storage blob upload should notify multiple Azure Functions through filterable event subscriptions. Which finding verifies its resolution?
Event Grid distributes discrete source events to configured subscribers. Confirm using the measurable result: Only event handlers matching the subject filter are invoked for the test upload.
Central secret retrieval separates sensitive credentials from source and build artifacts. The Key Vault app secrets test checks credential rotation works without modifying committed application configuration; the relevant outcome is Only event handlers matching the subject filter are invoked for the test upload.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The offered observation would demonstrate App Configuration feature flags: Pilot users see the feature after refresh and others retain the previous behavior. The current validation is different: Only event handlers matching the subject filter are invoked for the test upload.
Failure handling isolates unhealthy dependencies and avoids request pileups. The distinguishing check is: Only event handlers matching the subject filter are invoked for the test upload.
To validate the ExpressRoute private circuit deployment, reviewers revisit this operational need: A large enterprise needs private reliable WAN connectivity to Azure at scale. What result confirms it was met?
ExpressRoute links customer WAN to Azure backbone privately through provider connectivity. Confirm using the measurable result: A test workload reaches Azure over advertised private prefixes when one circuit path fails.
Private endpoints attach supported PaaS access to a private IP and require DNS resolution. The offered observation would demonstrate Private endpoint: The data source resolves to a VNet private address and public access is denied. The current validation is different: A test workload reaches Azure over advertised private prefixes when one circuit path fails.
NSGs provide stateful Layer 3/4 access rules rather than application-layer inspection. Those observations validate NSG subnet filtering. They do not establish the required ExpressRoute private circuit result: A test workload reaches Azure over advertised private prefixes when one circuit path fails.
VNet integration is principally an outbound feature; inbound private access requires other controls. The VNet integration App Service test checks the app connects to private SQL via VNet while its public frontend remains reachable as intended; the relevant outcome is A test workload reaches Azure over advertised private prefixes when one circuit path fails.
For Blob user-delegation SAS, operations are closing a change that addressed: A partner needs time-limited upload permission to a particular blob without sharing the storage account key. Which post-change signal belongs in the acceptance record?
A user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. Confirm using the measurable result: The permitted upload works before expiry while an unauthorized operation and expired token fail.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. The distinguishing check is: The permitted upload works before expiry while an unauthorized operation and expired token fail.
Immutable storage prevents overwrite and delete during the configured retention interval. The Blob immutability test checks an authorized user cannot modify a protected retained object before expiry; the relevant outcome is The permitted upload works before expiry while an unauthorized operation and expired token fail.
Blob change feed records changes to blob objects for downstream processing. The offered observation would demonstrate Blob change feed: The consumer reads expected object creation and deletion change records. The current validation is different: The permitted upload works before expiry while an unauthorized operation and expired token fail.
For the VM agentless migration requirement, the proposed architecture uses: Use an appropriate Azure Migrate server migration path after appliance assessment. Why does that design fit?
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. It is material here because vMware VMs need replicated migration to Azure with a controlled cutover and minimal app redesign.
Replatforming changes hosting characteristics while preserving most app behavior. It belongs to Replatform database. The stated architecture instead relies on: Server migration replication supports lift-and-shift of eligible VM workloads to Azure.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. That statement describes Rehost versus refactor, while the question asks how VM agentless migration works: Server migration replication supports lift-and-shift of eligible VM workloads to Azure.
Online migration reduces cutover downtime by applying ongoing changes after the baseline copy. Server migration replication supports lift-and-shift of eligible VM workloads to Azure.
A security team needs interactive time-series queries across petabytes of ingested machine events. Which Azure architecture would most directly achieve the required result: A filtered time-series KQL query returns the needed event trend within response goals?
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. The selected architecture is consider Azure Data Explorer with appropriate ingestion, partitioning and KQL queries; confirm the result by checking that a filtered time-series KQL query returns the needed event trend within response goals.
OneLake offers a common analytics data foundation for supported Fabric workloads. Its design target is Fabric OneLake analytics. The stated requirement instead concerns: A security team needs interactive time-series queries across petabytes of ingested machine events.
Tumbling-window triggers model contiguous time slices with support for backfill. It does not solve the specified Azure Data Explorer telemetry condition.
Serverless SQL queries external lake files with consumption-based query compute. That is useful for Synapse serverless SQL (Data analysts must run ad hoc SQL queries over Parquet files in a data lake without provisioning a cluster). It does not meet the current Azure Data Explorer telemetry requirement: A security team needs interactive time-series queries across petabytes of ingested machine events.
A legacy SQL database contains unsupported features and the team wants a target tier before moving. A deployment must satisfy this operational criterion: The compatibility report has no unmitigated blocking features for the chosen target. Which plan is appropriate?
Migration assessment identifies blockers and target-fit issues before a cutover. The selected architecture is run Azure SQL migration assessment and remediate feature compatibility findings; confirm the result by checking that the compatibility report has no unmitigated blocking features for the chosen target.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. The relevant requirement is: A legacy SQL database contains unsupported features and the team wants a target tier before moving.
Hyperscale decouples storage scale from compute and supports large database sizes. It does not solve the specified SQL migration assessment condition.
Read-only replicas can offload reporting from the primary where the tier provides the capability. Its design target is SQL read scaling. The stated requirement instead concerns: A legacy SQL database contains unsupported features and the team wants a target tier before moving.
A production app's manually changed resource settings diverge from the approved IaC template. An architecture board will approve a solution only if this outcome is demonstrated: The change report identifies manual drift and approved deployment restores the intended state. What should be selected?
Azure deployment what-if previews resource changes before applying a template. The selected architecture is use a what-if deployment comparison and controlled remediation for the declared configuration; confirm the result by checking that the change report identifies manual drift and approved deployment restores the intended state.
Workbooks provide interactive analytical reports rather than the policy enforcement mechanism itself. The current need is: A production app's manually changed resource settings diverge from the approved IaC template.
Subscriptions are billing and resource governance boundaries with independent quotas and RBAC assignment scopes. That is useful for Subscription isolation (A regulated subsidiary needs separate billing and policy boundaries from the parent business unit). It does not meet the current Deployment drift requirement: A production app's manually changed resource settings diverge from the approved IaC template.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It does not solve the specified Deployment drift condition.
Please check your mailbox for a message from support@examlabs.com and follow the directions.