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 solution must address both App Configuration feature flags and Web PubSub real time. First requirement: Operators must turn a feature on for a pilot group without rebuilding application binaries. Second requirement: A collaboration app must send real-time server-to-client notifications to many concurrent browsers. Select TWO recommendations that meet these independent needs.
For the Web PubSub real time half of this design, web PubSub provides managed WebSocket connection fan-out so application servers need not hold all client sessions. Check: Two connected clients immediately receive the authorized published event. The other half concerns App Configuration feature flags.
For the App Configuration feature flags half of this two-part design, app Configuration centralizes feature settings; secrets should remain in Key Vault. Verify: Pilot users see the feature after refresh and others retain the previous behavior. The other half concerns Web PubSub real time.
Queueing decouples front-end latency from downstream worker availability. This alternative solves Queue asynchronous processing, while the question separately requires App Configuration feature flags and Web PubSub real time.
Event Hubs provides a replayable ordered stream within partitions for large event volumes. The corresponding task is Event Hubs telemetry: Thousands of kiosks upload constant high-volume telemetry that several analytic consumers replay. It is not one of the two requested controls (App Configuration feature flags and Web PubSub real time).
Topics fan out a message to independently managed subscriptions with durable handling. That plan is appropriate for Publish subscribe topics. The two controls sought here are App Configuration feature flags and Web PubSub real time.
For Cross-region backup, operations are closing a change that addressed: An organization requires VM backup copies surviving the loss of an entire Azure region. Which post-change signal belongs in the acceptance record?
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. Confirm using the measurable result: A supported secondary-region restore yields the expected recovery point.
Backup-specific RBAC roles separate operational restore tasks from vault administration. The offered observation would demonstrate Backup vault access: A designated operator can restore an approved workload but cannot delete its vault. The current validation is different: A supported secondary-region restore yields the expected recovery point.
Compute replication does not automatically guarantee complete application network reachability. Those observations validate Azure-to-Azure ASR networking. They do not establish the required Cross-region backup result: A supported secondary-region restore yields the expected recovery point.
Blob operational backup relies on point-in-time object protection features rather than VM-level backups. The distinguishing check is: A supported secondary-region restore yields the expected recovery point.
A platform team needs custom Kubernetes network policies controllers and cluster API access. The acceptance test is: Custom controllers and policy resources function under the supported cluster configuration. Which design recommendation best satisfies both?
AKS provides managed Kubernetes control-plane hosting with configurable worker clusters. The selected architecture is select Azure Kubernetes Service with appropriate cluster management guardrails; confirm the result by checking that custom controllers and policy resources function under the supported cluster configuration.
Functions supplies event-driven serverless execution with plan-specific scale and timeout limits. The current need is: A platform team needs custom Kubernetes network policies controllers and cluster API access.
Compute Gallery distributes managed image versions for repeatable VM deployments. It does not solve the specified AKS full Kubernetes condition.
GPU instances provide accelerators not present on standard CPU-only VMs. The relevant requirement is: A platform team needs custom Kubernetes network policies controllers and cluster API access.
Security analysts require long-term sign-in analysis alongside cloud resource diagnostics. Choose the architecture that can be validated by this result: Risky sign-ins can be queried with resource access events over the chosen time window.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. The selected architecture is export supported Microsoft Entra sign-in logs using diagnostic settings to the approved workspace; confirm the result by checking that 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. That is useful for Web transaction traces (Users report failed checkout requests across a multi-tier web app and only CPU graphs are available). It does not meet the current Identity-signin monitoring requirement: Security analysts require long-term sign-in analysis alongside cloud resource diagnostics.
The Activity Log records Azure Resource Manager control-plane events independent of guest agents. The relevant requirement is: Security analysts require long-term sign-in analysis alongside cloud resource diagnostics.
VM insights and the agent collect supported guest operating-system counters and process data. It does not solve the specified Identity-signin monitoring condition.
Architecture review: VM guest performance and Control-plane audit. Requirement A: Server owners need guest memory and disk performance for VMs rather than only host-level platform metrics. Requirement B: A tenant auditor needs subscription-level records for resource create and delete operations, not VM guest logs. Which complete two-part proposal satisfies both constraints?
For requirement A, VM insights and the agent collect supported guest operating-system counters and process data. For requirement B, the Activity Log records Azure Resource Manager control-plane events independent of guest agents. Verify both independently: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor; A denied deployment and a successful resource deletion appear with caller and operation name.
This combines WAF decision logs and Azure service health, which do not satisfy the distinct requirements for VM guest performance and Control-plane audit.
The option covers one requirement but substitutes WAF decision logs for VM guest performance. The missing acceptance result is: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor.
One action is correct. The other targets Azure service health, leaving Control-plane audit unsolved. Its necessary action is: Route Azure Activity Log to a central Log Analytics workspace through diagnostic settings.
Before approving Policy exemption, the reviewer assesses this requirement: An acquired system has a temporary documented exception to an encryption rule with an expiration date. Which of the reported outcomes is decisive?
Policy exemptions record approved exceptions while the policy remains assigned. Confirm using the measurable result: The exception is visible in compliance reports and expires on the documented date.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. The offered observation would demonstrate Resource group lifecycle: Deleting an approved test resource group removes only the intended environment resources. The current validation is different: The exception is visible in compliance reports and expires on the documented date.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. The distinguishing check is: The exception is visible in compliance reports and expires on the documented date.
Modify effects can update eligible metadata and require the required remediation permissions. The Inherited tagging test checks new supported resources inherit the resource-group environment tag after assignment; the relevant outcome is The exception is visible in compliance reports and expires on the documented date.
Only rows changed since the last successful extraction should be copied from a large source database. Choose the architecture that can be validated by this result: A second run copies only new or modified rows and advances the checkpoint after success.
A stored watermark limits reads to changes after the last successful processed interval. The selected architecture is implement watermark-based incremental ingestion with persisted checkpoints; confirm the result by checking that a second run copies only new or modified rows and advances the checkpoint after success.
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. It does not solve the specified ADF incremental copy condition.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. That is useful for Databricks Delta Lake (An ETL architecture needs ACID updates and versioned tables over object storage for Spark workloads). It does not meet the current ADF incremental copy requirement: Only rows changed since the last successful extraction should be copied from a large source database.
Dedicated pools supply reserved MPP compute suited for managed warehouse workloads. Its design target is Synapse dedicated SQL. The stated requirement instead concerns: Only rows changed since the last successful extraction should be copied from a large source database.
The SOC streams resource events into an external SIEM and needs independent replay and consumer handling. An engineer must deliver the following acceptance evidence: A test operation appears in the Event Hub stream and can be read by the SIEM consumer. What design choice is defensible?
Event Hubs provides durable high-throughput event ingestion for downstream stream consumers. The selected architecture is route supported platform diagnostic events to an Event Hubs namespace; confirm the result by checking that a test operation appears in the Event Hub stream and can be read by the SIEM consumer.
Action groups define notifications and automated responses and can be reused by alert rules. Its design target is Notification routing. The stated requirement instead concerns: 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. The relevant requirement is: The SOC streams resource events into an external SIEM and needs independent replay and consumer handling.
Synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. It does not solve the specified Security-event streaming condition.
A production AKS cluster requires pods and nodes across three availability zones. Choose the architecture that can be validated by this result: After a simulated zone failure, surviving pods maintain API availability and replacement replicas become Ready within the tested recovery window on healthy-zone nodes.
Zonal placement reduces failure concentration, while recovery also requires remaining-zone capacity, quota, compatible persistent-volume topology and nonblocking pod scheduling rules. Use suitable per-zone pools and workload spread policies, verify node and pod readiness during a single-zone failure drill, and require that the API remains available while replacement replicas recover within the agreed window. Cluster Autoscaler is not inherently zone-aware and strict anti-affinity can leave pods Pending.
Fault injection tests whether resilience patterns work under realistic failure conditions. It does not solve the specified AKS availability zones condition.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. The current need is: A production AKS cluster requires pods and nodes across three availability zones.
A zone-separated standby supports automated failover where offered. That is useful for PostgreSQL zone redundant HA (A mission-critical PostgreSQL workload requires HA across zones within a region). It does not meet the current AKS availability zones requirement: A production AKS cluster requires pods and nodes across three availability zones.
To validate the VM maintenance handling deployment, reviewers revisit this operational need: A VM-based API must survive scheduled host maintenance without customer-visible downtime. What result confirms it was met?
Redundancy prevents a single host maintenance event from removing the only serving instance. Confirm using the measurable result: Maintenance on one node leaves other healthy nodes serving the API.
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 VM maintenance handling result: Maintenance on one node leaves other healthy nodes serving the API.
VMSS automates management and scaling of similar VMs in the same workload. The distinguishing check is: Maintenance on one node leaves other healthy nodes serving the API.
Durable Functions manages stateful workflows over serverless function executions. The Azure Functions durable workflow test checks a resumed orchestration continues from saved state after a worker restart; the relevant outcome is Maintenance on one node leaves other healthy nodes serving the API.
The Hub-spoke topology review proposes: Use a hub-and-spoke network topology with shared service governance. Which Azure behavior is the technical justification for this decision?
A hub centralizes connectivity services while spoke VNets isolate applications. It is material here because many app VNets need shared DNS firewall and on-prem connectivity without each owning a gateway.
VNet peering alone is not transitive and forwarding needs explicit architecture. It belongs to Peering nontransitivity. The stated architecture instead relies on: A hub centralizes connectivity services while spoke VNets isolate applications.
User-defined routes can override platform routing to steer approved subnets through an NVA/firewall. That statement describes UDR firewall inspection, while the question asks how Hub-spoke topology works: A hub centralizes connectivity services while spoke VNets isolate applications.
NAT Gateway provides outbound SNAT for supported subnet internet traffic. A hub centralizes connectivity services while spoke VNets isolate applications.
Please check your mailbox for a message from support@examlabs.com and follow the directions.