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 84

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.

Question 831

An Azure VM app-vm uses a subnet route table with a 10.90.0.0/16 UDR pointing to a firewall NVA. The administrator observes that packets sent to 10.90.4.20 instead leave through an unexpected next hop. Which Network Watcher check determines the actual selected route and next-hop device for that destination?

  1. Run IP flow verify to identify the NSG allow/deny decision but infer that it also selected the route.
  2. Run Network Watcher Next hop for app-vm and destination 10.90.4.20, then inspect effective routes if needed to explain the selection.
  3. Change the VM guest operating system DNS suffix and assume the routing next hop follows the suffix.
  4. Run a one-time TCP connect test and treat a timeout alone as proof of which UDR was chosen.

Explanation

Correct Answer

B:

Network Watcher Next hop reports the chosen next-hop type and, where applicable, next-hop address and route-table information for a VM destination IP. This makes it the direct test of whether a UDR toward the intended firewall is active or another route takes precedence. Inspect effective NIC routes afterward for route prefix and source context, including user-defined, BGP-propagated and system entries. The result identifies the actual forwarding decision without changing production routes just to troubleshoot.

Incorrect Answers

A:

IP flow verify tests a flow against network security group rules, returning the allow/deny decision and matched NSG rule. It does not tell the administrator which UDR or BGP/system route is winning for the given destination. Because the stated symptom is an unexpected next hop rather than an NSG block, use Next hop to inspect routing.

C:

DNS suffix settings influence how an unqualified hostname is resolved. The destination in this case is already a numeric IP address, so changing a DNS suffix cannot alter the route-selection logic for 10.90.4.20. Route selection depends on effective routes and prefix specificity, not client DNS search settings.

D:

A TCP connection attempt can reveal success or failure, but many causes such as NSG policy, guest firewall, the NVA and application state can create the same timeout. It does not identify the chosen next-hop route or device. Network Watcher Next hop specifically answers that routing question.

Question 832

An Azure VPN virtual network gateway has an unhealthy site-to-site connection to a branch office after an IPsec configuration change. Network engineers need a targeted diagnostic check of the gateway and connection, with resulting diagnostic files saved to an approved Azure Storage container. Which Azure Network Watcher feature should they run?

  1. IP flow verify on an unrelated VM NIC; it tests the VPN gateway's negotiated IKE and IPsec configuration.
  2. Azure Load Balancer backend health probes; they retrieve site-to-site VPN gateway connection logs into Azure Storage.
  3. Connection Monitor with a TCP test to the public DNS name of the branch router; it performs complete VPN gateway-specific configuration diagnostics.
  4. Network Watcher VPN troubleshoot on the virtual network gateway and relevant VPN connection, selecting a storage account/container for diagnostic logs.

Explanation

Correct Answer

D:

Network Watcher VPN troubleshoot accepts an Azure virtual network gateway or VPN connection as its diagnostic target and writes detailed diagnostic logs to the selected storage account/container. It is the documented gateway-level tool for investigating unhealthy site-to-site VPN connections.

Incorrect Answers

A:

IP flow verify checks whether a specific flow is allowed or denied by effective network security rules on a VM; it does not run dedicated VPN gateway or tunnel diagnostics.

B:

Load Balancer health probes evaluate backend endpoint health for the load balancer; they are unrelated to the VPN gateway's connection state and do not produce VPN troubleshoot logs.

C:

Connection Monitor is valuable for recurring transport reachability trends, but a TCP probe cannot replace gateway-specific VPN troubleshoot diagnostics of the Azure VPN gateway and its configured connection.

Question 833

VM `vm-web` intermittently receives TCP connection resets during responses from private service `10.6.2.5:443`, after a TCP session has already been established. Network Watcher IP Flow Verify permits the flow, Next hop shows the expected route, and the guest application log does not explain the resets. The approved Network Watcher VM extension is installed. Engineers need packet-level TCP flags and retransmission timing around the next short incident while limiting collected data. What should they do?

  1. Run IP Flow Verify again without collecting traffic; its allow result includes a transcript of TCP reset flags and packet timings.
  2. Open Network Watcher Topology for the resource group; its resource relationship graph includes packet payloads and per-flow TCP retransmission traces.
  3. Inspect Network Watcher Next hop for the destination again; route-selection output also records the application's TCP flag sequence for established connections.
  4. Run a short, authorized Network Watcher packet capture on `vm-web` with TCP address/port filters and a bounded duration; analyze the saved capture for resets and retransmissions.

Explanation

Correct Answer

D:

Network Watcher packet capture runs through its installed VM extension and can filter by five-tuple fields (addresses, ports and protocol). A time-bounded capture focused on the service flow provides the actual TCP control flags and timing evidence needed for the intermittent resets, without collecting unrelated network traffic.

Incorrect Answers

A:

IP Flow Verify checks the applicable NSG allow/deny result for the selected flow. It does not capture the actual packets or show which endpoint sent TCP RST flags, so repeating an already successful allow check cannot supply the missing evidence.

B:

Network topology diagrams resources and their relationships, not individual TCP packet flags and retransmission timing. A resource graph cannot replace a packet trace of a short-lived established-session failure.

C:

Next hop evaluates the routing decision for a destination and is already correct in this scenario. It does not record TCP segment fields, resets or retransmissions from the affected application session.

Question 834

An on-premises Windows server intermittently fails to open TCP/443 on vm-api in Azure over an approved VPN. Network operations needs repeated reachability and round-trip-time measurements over several days, rather than a one-time snapshot. Supported monitoring agents and Azure Network Watcher are available. Which TWO actions establish the measurement and yield evidence? Select TWO answers.

  1. Change the on-premises server’s DNS suffix without defining any connectivity checks.
  2. Create a Connection Monitor test group with the on-premises source, Azure VM destination, TCP/443 test configuration and required agent support.
  3. Run IP flow verify once on the Azure VM NIC and assume that single result captures intermittent VPN failures.
  4. Review Connection Monitor’s failed-check trends, latency and available path observations across the scheduled interval.
  5. Disable VPN routing and rely on a public IP for the previously private endpoint.

Explanation

Correct Answers

B:

Connection Monitor uses sources, destinations, test configurations and test groups to run repeated checks. Define the on-premises agent as a supported source, vm-api as the destination and TCP/443 with an appropriate interval and thresholds. This creates observations across the VPN path rather than a single attempt, provided network permissions and monitoring agents are configured correctly. Once checks run, inspect results instead of assuming that creating the monitor alone proves path health.

D:

Connection Monitor reports per-test check failures and round-trip times over time. Comparing results around incident periods can show whether reachability drops correlate with route or network events, and available topology views can guide investigation. On-premises path topology visibility has limitations, so avoid claiming exact hop attribution without evidence. Interpreting the collected trend completes the investigation alongside configuring the specific scheduled test.

Incorrect Answers

A:

A DNS suffix can influence hostname lookup, but the request is for repeated evidence about a known TCP path. No name-resolution failure is asserted, and renaming search suffixes neither collects round-trip-time data nor explains intermittent VPN behavior. A connection monitor with explicit endpoints and a protocol-specific test is the appropriate scheduled measurement approach.

C:

IP flow verify checks whether an NSG rule permits or denies a particular five-tuple at a point in time. That can be valuable during focused security troubleshooting, but a single success or failure does not characterize multi-day intermittent VPN latency or reachability. The prompt requires a scheduled series of observations, which calls for Connection Monitor tests.

E:

Switching the application to a public IP bypasses the approved private VPN path and changes the security architecture. It would not measure or explain the intermittent failures that occur on the existing connection. The team needs evidence to diagnose the private connectivity issue before considering redesign, not an unrelated public access workaround.

Question 835

Azure Bastion initiates TCP/22 to vm-build at 10.50.0.5 from subnet 10.50.1.0/26. An Azure Virtual Network Manager security admin Allow rule and the VM subnet NSG both permit the flow, yet an attached NIC NSG might deny it. The investigator needs one simulated-flow report showing matching decisions from the central security admin rule, subnet NSG and NIC NSG—not a topology diagram. Which tool should be used?

  1. Run Azure Network Watcher NSG diagnostics for the VM target, inbound TCP traffic, Bastion source subnet, destination IP and port 22, then examine the matching rules reported at each applicable layer.
  2. Open Network Watcher Topology to view the Bastion and VM resource relationships and assume each connection line proves that TCP/22 is allowed by every applicable NSG.
  3. Use Network Watcher Next hop from the VM toward the subnet, then assume that an expected route automatically supersedes security admin and NIC NSG Deny rules.
  4. Turn on VM Insights CPU charts; the presence of an Azure Monitor Agent on the VM exposes the matched network security rules for TCP/22 without a diagnostic flow check.

Explanation

Correct Answer

A:

Network Watcher NSG diagnostics evaluates a specified flow against applicable Azure Virtual Network Manager security admin rules and subnet/NIC NSGs. Its detailed rule results can reveal an Allow at central/subnet layers and a Deny on the VM NIC, explaining why Bastion cannot complete SSH even though a portion of the policy allows it.

Incorrect Answers

B:

Topology describes supported network resources and connections; it does not report each applicable security rule's matching action for this inbound TCP/22 flow. The observed allow/deny discrepancy requires flow-specific rule diagnostics.

C:

Next hop identifies routing behavior, not the effective allow/deny decisions across centrally managed security admin rules and both NSG attachment points. A valid route does not override a NIC NSG Deny.

D:

VM Insights collects guest/system performance telemetry; CPU metrics or an installed monitoring agent alone cannot adjudicate a network security policy match for a specified source/destination/port.

Question 836

A production virtual network still has an older NSG flow-log resource enabled on its subnet NSG. The security team must keep IP-flow metadata across the entire virtual network through 2028 and avoid duplicate records and processing charges during migration. New NSG flow-log resources are no longer supported and existing NSG flow logs retire September 30, 2027. The team has an approved Storage account for the new logs. What migration sequence should it use?

  1. Create a fresh NSG flow-log resource on every NIC and subnet in 2026 because new NSG flow-log creation is supported until September 2027.
  2. Disable existing NSG flow logs immediately and substitute a periodic Network Watcher IP flow verify check; simulated flow allow/deny decisions provide an equivalent persistent traffic history.
  3. Continue relying only on the current NSG flow logs through 2028 and increase their storage retention, because the planned 2027 retirement affects only the portal but not NSG flow-log generation.
  4. Enable Azure Network Watcher virtual network flow logs on the VNet with the approved storage destination, confirm that current five-tuple flow events are recorded (and Traffic Analytics if needed), then disable the overlapping legacy NSG flow-log resource.

Explanation

Correct Answer

D:

VNet flow logs are the supported replacement, capture actual Layer 4 IP flow metadata across a virtual network and can export records to Azure Storage and Traffic Analytics. Microsoft recommends validating that replacement flow logs exist before disabling overlapping NSG flow logs to avoid duplicate flow recording and cost, while preserving the approved retention of previously stored data.

Incorrect Answers

A:

Microsoft stopped supporting the creation of new NSG flow logs on June 30, 2025, even though existing NSG flow logs remain available until the September 30, 2027 retirement. Attempting to create new NSG flow-log resources is not the migration path, and NIC/subnet NSG scope does not provide the full VNet visibility requested.

B:

Network Watcher IP flow verify tests a specified simulated flow against security rules at a moment in time. It does not continuously record actual observed network traffic across the VNet. Disabling the old logging before confirming a replacement leaves an evidence gap.

C:

The documented NSG flow-log retirement ends the feature and removes existing flow-log resources after September 30, 2027. Previously stored data may remain subject to Storage retention, but it does not mean future NSG flow events continue to be generated through 2028.

Question 837

A TCP/443 test from an Azure VM to an internal application still times out after IP Flow Verify reports Allow and Network Watcher Next hop confirms the intended UDR path. The team needs a one-time end-to-end diagnosis of transport connectivity and possible guest firewall or destination socket issues. Which Network Watcher feature is best?

  1. Run IP Flow Verify again for the same five-tuple and assume its Allow result confirms successful TCP establishment.
  2. Rename the VM resource-group tag to override the Azure packet route and restart all virtual machines.
  3. Run Network Watcher Connection troubleshoot from the source VM to the destination IP or FQDN on TCP 443, including relevant connection/NSG/route diagnostics.
  4. Delete the VNet and redeploy the VM to reset the routing table rather than perform a targeted connection test.

Explanation

Correct Answer

C:

Connection troubleshoot tests connectivity from a supported source to a destination and can report transport connectivity, NSG checks, next-hop problems, DNS issues and potential guest firewall/socket failures. With IP Flow Verify and the next hop already cleared, it provides the relevant targeted end-to-end diagnosis.

Incorrect Answers

A:

IP Flow Verify evaluates NSG allow/deny for a specified flow. An Allow decision does not prove the remote application listens on TCP 443 or that transport connectivity succeeds. Repeating it cannot diagnose an already-known non-NSG timeout.

B:

Resource-group tags are organizational metadata and do not rewrite packet routes or restart network services. This action is unrelated to transport reachability and risks making a production issue worse.

D:

Deleting a VNet would disrupt unrelated resources and is not a diagnostic method. An Azure Network Watcher connection test can identify the failing segment without recreating working infrastructure.

Question 838

A running Azure Network Watcher Connection Monitor TCP test has a configured failed-check percentage threshold of 30% and a round-trip time threshold of 200 ms. In the current evaluated period, 25% of TCP checks failed and measured RTT is 110 ms. The monitor has valid test data. According to Connection Monitor threshold-state semantics, which state is expected?

  1. Fail, because any failed TCP check must set the test to Fail even when a higher percentage threshold was explicitly configured.
  2. Warning, because 25% is below the 30% failure threshold but above 80% of that threshold (24%), while 110 ms remains below the 200 ms RTT threshold.
  3. Pass, because a test with a defined 30% failure threshold cannot warn until exactly 30% checks fail.
  4. Indeterminate, because Connection Monitor produces a status only for HTTP tests and never evaluates configured TCP failed-check or RTT thresholds.

Explanation

Correct Answer

B:

Connection Monitor marks Warning when the failed-check percentage exceeds 80% of a configured failure threshold without exceeding the full failure threshold. Here 0.8 × 30% = 24%; 25% exceeds 24% but stays below 30%. RTT 110 ms stays below the 200 ms bound, so Warning is the appropriate observed state.

Incorrect Answers

A:

For Connection Monitor a configured threshold controls failure detection. A few failed TCP checks do not automatically mean Fail when the percentage remains below the explicitly selected 30% threshold and the RTT bound is not exceeded.

C:

Warning is an intermediate state rather than a threshold equality condition. The test has crossed the documented warning band because 25% is greater than 24%; labeling it Pass would hide the deteriorating connectivity.

D:

TCP and ICMP Connection Monitor tests track failed-check percentages and round-trip time. Indeterminate refers to unavailable test/log data; this scenario provides completed TCP measurements and valid threshold inputs.

Question 839

A client VM in spoke VNet `vnet-orders` cannot access `stledger.blob.core.windows.net` after a private endpoint was approved for the Blob service. The private endpoint NIC has address `10.30.4.9`, and the expected TCP/443 route and security rules have already been validated. Network Watcher Connection troubleshoot from the actual client VM reports a DNS-resolution failure for the storage FQDN, so no successful TCP test has yet occurred. Which next diagnostic and correction directly targets the demonstrated fault?

  1. Run Network Watcher IP flow verify for a guessed TCP packet and interpret any Allow outcome as proof that the Blob service FQDN resolves to the private endpoint address.
  2. Change Connection troubleshoot to target only literal IP 10.30.4.9 and record that private endpoint DNS works if a raw TCP probe connects, leaving the original failing hostname unresolved.
  3. Disable private endpoint routing and permit public Blob access because a DNS lookup failure proves that the approved private endpoint IP is invalid.
  4. From the affected VM, query `stledger.blob.core.windows.net`, inspect the `privatelink.blob.core.windows.net` private DNS record and relevant VNet link/custom DNS forwarding, correct resolution to `10.30.4.9`, and then rerun Connection troubleshoot by original FQDN on TCP/443.

Explanation

Correct Answer

D:

Microsoft directs administrators to run FQDN-based Connection troubleshoot from the source VM and compare the resolved DNS IP with the private endpoint NIC address. Incorrect results require checking the private DNS zone A record, linked VNet or the custom DNS forwarding chain. Once the original FQDN resolves to 10.30.4.9, rerun the TCP/443 test to distinguish remaining transport problems. This addresses the documented DNS failure instead of changing unrelated NSG/routing settings.

Incorrect Answers

A:

IP flow verify evaluates effective security rule decisions for a specified flow. It does not perform the querying VM’s DNS lookup for the storage account hostname and cannot prove which public or private IP that client receives. The failure was identified before a usable TCP probe.

B:

A successful raw-IP TCP probe would help isolate transport connectivity, but it bypasses the hostname resolution path actually used by the application. The reported DNS-resolution failure remains unresolved, so declaring the private endpoint DNS healthy would be incorrect.

C:

The endpoint connection is approved, and the NIC has an assigned private IP. Public exposure neither repairs the client’s broken private DNS resolution nor satisfies the secure private access requirement; it unnecessarily changes the permitted network boundary.

Question 840

The finance team has a single production Windows VM in eastus, no Recovery Services vault, no Azure Backup policy, and no other backup configuration. Policy requires daily Azure VM recovery points retained for 30 days. Which TWO actions establish protection for this VM? Select TWO answers.

  1. Enable Storage Blob soft delete on an unrelated general-purpose storage account and assume VM disk recovery points appear.
  2. Move the VM to westus before creating an eastus Recovery Services vault, although the workload must remain in eastus.
  3. Select or create a supported daily Azure VM backup policy in the vault and enable backup protection for the VM under that policy.
  4. Create a Recovery Services vault in the VM’s supported region with appropriate access and redundancy configuration.
  5. Assign the VM the Azure subscription Owner role; management rights alone automatically schedule recovery points.

Explanation

Correct Answers

C:

Azure VM backup uses policies to establish when recovery points are created and how long they are retained. In the eligible Recovery Services vault, select or create a supported policy meeting the daily schedule and 30-day retention, then enable protection for the VM. This turns the policy into an operating backup configuration rather than merely a document or an alert. Confirm the initial backup job completes and that the resulting recovery points meet the contractual cadence.

D:

A Recovery Services vault is the Azure Backup resource that stores and governs VM recovery points. Create it in the supported region for the eastus VM and choose the required access and redundancy defaults for the backup data. The vault is the prerequisite target for the policy and VM protection operation. Vault creation alone does not start backups; the complementary selection and enablement of the VM policy are separately necessary.

Incorrect Answers

A:

Blob soft delete protects eligible deleted blob objects and does not schedule Azure VM snapshots or vault recovery points for this instance. No current VM backup configuration exists. The administrator needs a Recovery Services vault and a VM backup policy with protection enabled, not a generic blob feature on an unrelated account.

B:

Azure VM backup normally uses a Recovery Services vault in the same region as the protected VM, and the business has not approved a VM relocation. Moving a production VM to another region creates needless operational change without configuring backup protection. Create an eligible vault in the VM’s current region and enable protection there instead.

E:

Azure subscription Owner is a broad control-plane permission, not a scheduled backup policy. Giving the VM or an administrator this role would not create recovery points by itself and is excessive for the stated task. Backup must be configured through an eligible Recovery Services vault, the VM workload and an actual backup policy.