mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 83

Question 820

A company still runs the legacy VM Insights Map and Dependency Agent to visualize connections between processes on Azure virtual machines and external services. The team needs ongoing process-dependency discovery after the June 30, 2028 retirement, while retaining currently supported VM performance monitoring. Which transition follows Microsoft guidance?

  1. Keep onboarding new VMs to the Dependency Agent and assume the Map REST API will remain supported indefinitely.
  2. Stop using Azure Monitor Agent and disable all VM Insights performance monitoring because the Map feature is retiring.
  3. Replace process-connection topology with Azure Storage Insights availability and transaction charts.
  4. Offboard the Dependency Agent/Map, evaluate a supported monitoring and diagnostics replacement for process dependencies, and continue Azure Monitor Agent-based VM performance monitoring.

Explanation

Correct Answer

D:

Microsoft specifically recommends offboarding VM Insights Map and the Dependency Agent before June 30, 2028. For process and external-service dependency discovery, it directs customers to evaluate replacement solutions in the Azure Marketplace monitoring and diagnostics category. VM Insights performance monitoring using Azure Monitor Agent is not affected and can continue. This plan replaces only the retiring dependency capability while retaining the supported performance-monitoring channel.

Incorrect Answers

A:

Microsoft is retiring the Dependency Agent and VM Insights Map, including the Map view, Connections Overview workbook, new data ingestion, and Service Map API support. Continuing to onboard additional virtual machines is not a supported long-term plan. The old data remains subject to workspace retention, but cannot be treated as a substitute for ongoing process-dependency collection after retirement. This option leaves the team dependent on technology Microsoft has explicitly deprecated.

B:

VM Insights performance monitoring uses Azure Monitor Agent, not the retired Dependency Agent. Microsoft says that performance monitoring remains supported when VM Insights Map retires. Disabling the agent would remove useful host performance telemetry without solving process-dependency discovery. The retirement announcement concerns Map and its dependency collection path, not all performance workbooks or VM Insights metrics.

C:

Azure Storage Insights reports storage-account activity such as availability, latency, and transactions. It does not discover process relationships on virtual machines or provide the connection topology previously collected by Dependency Agent. A storage dashboard can complement a broader monitoring strategy, but it cannot replace the missing process and external-service dependency graph for the stated requirement.

Question 821

Azure Storage Insights shows that storage availability is poor only for one storage account. The team needs its time-series request count, latency and availability trend before changing network rules. Which monitoring approach directly answers the question?

  1. Install Azure Monitor Agent into a VM unrelated to the storage account and read only guest disk queue counters.
  2. Change the storage account access tier to Archive so all request failures are hidden from reporting.
  3. Use the account-specific Azure Storage Insights view and correlate its transaction, availability, and latency metrics for the same period.
  4. Configure a Network Security Group on a virtual machine; this automatically reports all storage data-plane error codes.

Explanation

Correct Answer

C:

Storage Insights is designed to present account-level usage, availability, performance and failure trends, suitable for locating the affected request period.

Incorrect Answers

A:

Guest VM disk queue counters are not the storage service’s account-level transaction and availability telemetry.

B:

Changing object tier is a data-management action; it does not diagnose why storage requests were failing.

D:

VM network security group rules do not directly generate complete Azure Storage service error and latency metrics.

Question 822

An Azure administrator needs to diagram how VNets, virtual-network gateways, peerings, NSGs and attached VMs relate across two resource groups during a planned network change. The requirement is an interactive resource-relationship topology, not application HTTP traces or guest-memory graphs. Which Azure monitoring surface directly provides that view?

  1. Enable Azure VM Insights guest counters; memory and CPU measurements automatically draw all cross-resource network relationships.
  2. Use Storage Insights to graph Blob transaction statistics; it discovers VNet gateway and peering topology.
  3. Configure only Azure Monitor Agent collection rules on VMs; those rules generate the interactive network-resource topology without another tool.
  4. Open Network Watcher Topology (or Azure Monitor Network Insights topology), select the intended scope, and inspect the Azure networking resource relationships.

Explanation

Correct Answer

D:

Network Watcher topology displays supported Azure network resources and their relationships across selected subscriptions, resource groups and regions, matching the planned architecture diagram need.

Incorrect Answers

A:

VM Insights collects and visualizes VM performance and dependency telemetry; guest counters alone are not an interactive inventory of VNet, gateway and NSG resource relationships.

B:

Storage Insights is centered on storage account metrics. Storage transactions cannot supply the requested virtual-network resource graph.

C:

Azure Monitor Agent and data collection rules collect supported telemetry but do not replace the dedicated Azure Network Watcher topology view of network resources.

Question 823

Azure Monitor Agent is installed on Windows VM `vm-accounting`. An associated data collection rule already collects the guest counter `\Memory\Available MBytes` into Log Analytics workspace `law-ops` using the `Microsoft-Perf` stream. Recent samples are visible in the workspace's `Perf` table. A new workbook incorrectly queries only `InsightsMetrics | where Namespace == "Memory" and Name == "AvailableMB"` and returns nothing. Without reinstalling the agent or changing successful ingestion, what should the workbook query instead?

  1. Query `Perf` for `ObjectName == "Memory"` and `CounterName == "Available MBytes"`, using `CounterValue` with `TimeGenerated` and the VM identity to graph the memory series.
  2. Reinstall Azure Monitor Agent on `vm-accounting` even though the Windows counter is already visible in `Perf`; the installed agent prevents VM Insights memory queries.
  3. Enable the `Microsoft-InsightsMetrics` stream in an unrelated Storage account diagnostic setting; that will transform the VM's existing `Perf` data into InsightsMetrics records.
  4. Chart the VM's platform `Percentage CPU` metric and relabel it `Available MBytes`; the platform CPU value equals the guest available-memory count.

Explanation

Correct Answer

A:

The existing DCR sends Windows guest performance counters to the Log Analytics `Perf` table. Filtering its documented `ObjectName`, `CounterName`, `CounterValue`, `TimeGenerated` and VM identity fields reads the data that actually exists and yields a valid guest-memory chart without another collector or data-routing change.

Incorrect Answers

B:

Because current `Perf` samples already prove the agent and DCR are operating, reinstalling Azure Monitor Agent does not repair a query pointed at the wrong log table. It can cause avoidable disruption while leaving the workbook's InsightsMetrics query unchanged.

C:

An unrelated Storage resource's diagnostic settings do not re-route previously collected VM guest counters. `Microsoft-Perf` and `Microsoft-InsightsMetrics` are distinct DCR stream destinations; for the stated requirement, querying the populated `Perf` table is sufficient and avoids changing ingestion.

D:

Percentage CPU is a compute-utilization platform metric, not the Windows guest `Memory\Available MBytes` counter. Renaming a CPU chart would misrepresent the telemetry and would not expose memory amounts collected by the DCR.

Question 824

A workload's Insights dashboard reports no data for new VMs. What is the most appropriate next administrative decision?

  1. Use VM Insights/workbooks with appropriate scope and workspace data.
  2. Integrate Application Insights for the application rather than VM host metrics alone.
  3. Verify the Azure Monitor Agent, DCR association and workspace permissions.
  4. Enable VM Insights and required Azure Monitor Agent/data collection rules.

Explanation

Correct Answer

C:

VM Insights and guest telemetry rely on Azure Monitor Agent collection and correctly scoped data collection rules and destination workspaces. For missing data from newly onboarded VMs, check installed agent health, DCR association, collection content and workspace/network authorization before assuming the infrastructure is healthy or the dashboard has a display bug.

Incorrect Answers

A:

VM Insights/workbooks visualize already collected VM telemetry; a dashboard alone cannot repair an absent agent/DCR association or instrument web request traces.

B:

Application Insights tracks instrumented application requests/dependencies, not the host's memory metrics or cross-account storage transaction health.

D:

Agent and DCR setup generates VM telemetry; it doesn't by itself select a network topology or trace application requests.

Question 825

A .NET API runs on Azure App Service and returns occasional HTTP 500 responses even though host CPU and memory look normal. Developers need per-request timings, exception traces and duration of outbound SQL/HTTP dependencies to isolate the failing request path. Which telemetry should they enable?

  1. Enable VM Insights on a separate jump-box VM; its guest memory counters will automatically trace the App Service HTTP request and SQL calls.
  2. Configure Application Insights instrumentation for the API (for example supported OpenTelemetry/SDK collection) and review request, exception and dependency telemetry.
  3. Create a VM Insights workbook with CPU metrics only and infer the SQL operation causing each exception.
  4. Enable Azure Storage Insights on an unrelated account to capture the application’s HTTP pipeline and unhandled exceptions.

Explanation

Correct Answer

B:

Application Insights tracks instrumented requests, exceptions and external service calls and can correlate timing across dependencies, providing the required application-layer diagnosis.

Incorrect Answers

A:

VM Insights captures VM/guest performance; an unrelated jump-box cannot instrument the running App Service API request spans and downstream dependencies.

C:

A workbook can visualize existing metrics but does not generate request IDs, exceptions and dependency spans that were never instrumented.

D:

Storage Insights focuses on account transactions and latency, not .NET App Service exception stack traces or the application’s SQL/HTTP request dependency graph.

Question 826

An analyst compares different storage accounts with very different transaction volumes. Which Azure configuration or procedure is the best fit?

  1. Inspect Insights metrics and correlated logs to determine actual workload impact.
  2. Normalize error rates/latency across comparable metrics rather than raw failure counts alone.
  3. Integrate Application Insights for the application rather than VM host metrics alone.
  4. Enable VM Insights and required Azure Monitor Agent/data collection rules.

Explanation

Correct Answer

B:

A high-volume storage account may have more failed requests in absolute terms even when its failure rate is better. Compare rates and appropriate latency percentiles or other normalized metrics over matching windows to distinguish scale from degraded reliability.

Incorrect Answers

A:

Inspecting correlated logs and service-impact metrics is useful after finding an anomaly, but raw failure totals from accounts with different transaction volumes are not directly comparable. Compute failure rates or comparable latency/availability ratios over matching time windows and dimensions before ranking the accounts.

C:

Application Insights instrumentation produces request and dependency telemetry for specific applications. The analyst needs comparable platform transaction metrics across storage accounts with different traffic volumes, which Storage Insights provides instead.

D:

VM Insights with the Azure Monitor Agent and suitable collection rules provides VM guest and process telemetry, not comparable transaction/error rates for different storage accounts. Comparing raw errors across accounts with different volumes is misleading; normalize against total operations and inspect matching latency/availability metrics and time windows.

Question 827

A fleet of monitored Azure VMs already has VM Insights guest counters in one Log Analytics workspace. Operations wants an out-of-box Top N comparison of VM performance counters without creating a separate dashboard per VM. What should they open?

  1. The VM Insights single-VM topology diagram only, which cannot compare performance of several machines.
  2. Application Insights live metrics for a web app; it automatically analyzes every VM guest counter.
  3. The VM Insights multiple-VM Performance or Performance counters workbook scoped to the monitored fleet.
  4. A Recovery Services vault backup policy, which automatically visualizes CPU Top N counters.

Explanation

Correct Answer

C:

The supplied VM Insights multi-machine workbooks include Performance and Performance counters views for comparing monitored VM metrics.

Incorrect Answers

A:

A single-machine topology alone does not provide the multi-VM Top N performance workbook report requested.

B:

Application Insights collects application/request telemetry, not automatically all VM Insights performance counter comparisons.

D:

A VM backup retention policy controls restore-point schedules and does not provide the guest performance Top N workbook.

Question 828

A .NET checkout API already sends request, dependency, and exception telemetry to Application Insights. The Performance view shows that the `POST /checkout` operation has a sharp increase in response time, while the App Service host CPU remains normal. Operations must identify whether a SQL dependency, an external payment call, or application code dominates individual slow request transactions, without first changing the app instrumentation. What should the analyst open?

  1. Use the Azure subscription Activity Log to examine create/delete management events; its administrative record timings are equivalent to the checkout request spans.
  2. Create an Application Insights Standard availability test against the public health endpoint and treat a successful response as proof that no single checkout dependency is slow.
  3. Open Azure Storage Insights for an unrelated diagnostics storage account and rank its Blob Transactions metric; it identifies the SQL and external payment spans for the checkout request.
  4. Open the checkout operation in Application Insights Performance, drill into representative slow samples, and inspect End-to-end transaction details for the captured request, dependency durations, and exception context.

Explanation

Correct Answer

D:

Microsoft documents drilling from Application Insights Performance to representative operations and End-to-end transaction details. With request/dependency/exception telemetry already captured, the analyst can inspect the timing of the checkout request and its outbound calls and any captured exceptions, isolating the cause of latency without re-instrumenting the application.

Incorrect Answers

A:

The Azure Activity Log records Azure management-plane events, not the instrumented execution path for individual HTTP checkout requests or dependency spans. It cannot attribute a slow checkout transaction to its SQL and payment calls.

B:

Synthetic Standard availability tests are useful for testing public endpoint reachability and TLS responsiveness, but the health endpoint can succeed while the checkout operation has a slow database or payment dependency. They do not replace already-captured per-operation transaction diagnostics.

C:

Storage Insights describes storage account transactions, latency and availability. The scenario’s SQL and external-payment dependencies are emitted by the instrumented checkout application, not inferred from an unrelated storage account metric.

Question 829

A public Azure App Service API has a health endpoint at https://api.contoso.example/health. Requests from actual users are sporadic, but operations must test HTTP success and TLS certificate validity every few minutes from several geographic locations—even during hours with no real user traffic. The API cannot be modified. Which Azure Monitor feature fits?

  1. Create an Application Insights Standard availability test for the publicly reachable health URL, select several test locations and success/TLS criteria, and configure the resulting availability alert.
  2. Enable only VM Insights guest CPU counters on the App Service worker; they generate synthetic HTTP requests and validate the public certificate automatically.
  3. Use Azure Storage Insights for an unrelated Blob account and interpret its availability metric as HTTP health for the API.
  4. Inspect server-side request telemetry only; the absence of real requests guarantees a successful HTTP test from each external region.

Explanation

Correct Answer

A:

Application Insights Standard availability tests issue recurring synthetic HTTP/HTTPS requests to a publicly reachable endpoint from selected geographic locations without application code changes. They can evaluate response success and TLS certificate validity and generate alerts. This tests external availability, not only recorded real-user traffic or storage-service metrics.

Incorrect Answers

B:

VM Insights is designed around VM telemetry and does not by itself perform an internet-facing HTTP request or certificate validation against the App Service API. CPU measurements cannot prove remote public availability.

C:

Storage Insights summarizes platform metrics for storage accounts. The test target is an App Service HTTP endpoint; a different Blob account's availability does not establish the API response or TLS validity from external test locations.

D:

If real-user traffic is absent, server-side request telemetry may show no samples, not proof of health. A synthetic availability test actively makes requests on schedule and can detect outages before a customer generates traffic.

Question 830

Network operations reports SSH timeouts from VM vm-tools (10.12.1.6) to VM vm-prod (10.12.2.7) on TCP/22. Both are in Azure and the destination VM has an NSG at subnet and NIC scope. The engineer must identify which NSG rule permits or denies this specific flow, without changing any rules first. Which Network Watcher diagnostic is most appropriate?

  1. Connection Monitor, which observes reachability across repeated tests but does not return the one NSG rule evaluation for the chosen five-tuple.
  2. Next hop, which reports routing next-hop information for a destination but not the matching NSG permit/deny rule.
  3. IP flow verify using the destination VM NIC, direction, source/destination IPs, protocol and TCP ports.
  4. Effective routes at the VM NIC, which describe selected routing prefixes rather than the specific NSG security-rule decision.

Explanation

Correct Answer

C:

IP flow verify evaluates a packet tuple against applicable Azure network security group rules and reports whether traffic is allowed or denied, along with the matched rule. Enter the appropriate VM interface and flow direction, source and destination IP addresses, TCP protocol and ports. This directly determines whether the SSH timeout is attributable to an NSG decision. If the flow is allowed, subsequent diagnostics should examine route, guest firewall or SSH daemon rather than assume all connectivity failures are caused by NSGs.

Incorrect Answers

A:

Connection Monitor can gather recurrent connectivity and latency observations, which helps diagnose intermittent path problems. This task instead seeks the NSG rule that evaluates one specified TCP/22 flow right now. A repeated reachability test does not directly replace IP flow verify’s targeted security rule result for the VM network interface.

B:

Next hop answers which route and next-hop type the VM will use to reach a destination. It does not identify the subnet or NIC NSG rule that allows or denies a packet. The administrator already has a specific source/destination and port; choose IP flow verify for the requested packet-filter diagnosis.

D:

Effective routes list the route table entries applicable to a network interface. They are valuable when traffic follows an unexpected path, but the output is not an NSG rule-match evaluation. A correct route can coexist with a denying NSG. Use IP flow verify to test the specific flow against NSG security rules.