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 67

Question 660

Two Azure VNets show peering status Connected, but a TCP service in the remote spoke is unreachable. Which controls should be inspected before deleting peering?

  1. The VM desktop background and display-resolution setting.
  2. The storage account Blob lifecycle management policy.
  3. The public DNS TTL, even though private IP connectivity is the failing path.
  4. The effective routes, peering allow settings, source/destination NSGs and any central firewall/NVA path.

Explanation

Correct Answer

D:

A Connected peering alone does not guarantee permits in NSGs, forwarding rules or the effective route table.

Incorrect Answers

A:

GUI preferences do not affect Azure packet routing.

B:

Blob lifecycle rules govern stored objects, not peered VNet TCP reachability.

C:

DNS TTL cannot explain failed reachability when using an already-resolved private IP.

Question 661

An Azure VM reaches a private backend by IP address but cannot resolve the backend’s expected hostname. Which troubleshooting layer should be addressed first?

  1. Increase the VM disk size to allocate more DNS memory.
  2. Assign an Azure Owner role to the client VM’s managed identity.
  3. Inspect the configured DNS server, private zone links/records and resolver reachability for the requested name.
  4. Remove an NSG deny rule for TCP 443 without verifying whether name lookup succeeds.

Explanation

Correct Answer

C:

Successful direct-IP communication suggests packet forwarding works; investigate private DNS records and resolver settings.

Incorrect Answers

A:

Disk capacity does not provide DNS records or resolver connectivity.

B:

Azure management RBAC cannot make a DNS name resolvable.

D:

Changing the application TCP port filter does not correct a failed DNS query.

Question 662

A VM has a valid Azure route and permissive NSG rules but SSH still times out. What should the administrator do to resolve this specific case?

  1. Check firewall rules and return route, not just subnet NSG.
  2. Check the guest OS firewall and SSH daemon listener rather than modifying Azure route tables.
  3. Test private route and effective NSG policy plus the guest RDP listener and firewall, rather than attach a public IP.
  4. Add explicit routed hub path or direct peering; peering is nontransitive.

Explanation

Correct Answer

B:

If Azure routing and NSG filtering are valid, inspect the Linux guest firewall, sshd process, listening address/port and host network stack. Test the actual destination port from an appropriate source. An Azure route being present does not guarantee that the guest operating system accepts connections.

Incorrect Answers

A:

Firewall and return-route checks help when responses leave over an unexpected path or a network firewall drops packets. Here Azure routing and NSG allow traffic, so those network checks alone cannot establish whether sshd is running or the Linux guest firewall accepts the SSH listener port.

C:

The suggested diagnostic targets a private RDP connection to a Windows VM and its RDP service. This VM fails SSH, and a known valid Azure route/NSG path makes the guest SSH daemon and host firewall the next checks, not a Windows RDP listener or VPN-specific test.

D:

Adding a directly peered or hub-transit route fixes a missing network path, because VNet peering is not inherently transitive. The scenario states that Azure routing is already valid, so changing peering topology does not diagnose a stopped SSH daemon or guest firewall deny rule.

Question 663

A VM has no public IP, its corporate VPN is connected, but RDP to the private NIC address times out. Which change addresses the stated situation most precisely?

  1. Check the guest OS firewall and SSH daemon listener rather than modifying Azure route tables.
  2. Renumber/translate routes to eliminate ambiguity for intended traffic.
  3. Test private route and effective NSG policy plus the guest RDP listener and firewall, rather than attach a public IP.
  4. Validate the actual destination listener/port and NSG policy.

Explanation

Correct Answer

C:

With the VPN connected and no VM public IP, test the path to the VM's private NIC address using effective routes, subnet/NIC NSG rules and a tool such as connection troubleshoot. Also confirm the Windows guest firewall and RDP service listen on the intended port. None of these checks requires opening the VM to the public internet.

Incorrect Answers

A:

Checking sshd and a Linux guest SSH firewall is mismatched to a Windows RDP timeout over the corporate VPN. Even though guest filtering matters, the required listener is RDP rather than SSH; the engineer should examine the end-to-end private route and TCP 3389 controls.

B:

Address overlap on the VPN can cause asymmetric or ambiguous routing, but the scenario gives no evidence of overlapping prefixes. Renumbering or translating networks before inspecting effective routes and connection results is an unnecessary disruptive step.

D:

A generic port/listener investigation can help in many connection failures, but by itself it omits the stated VPN-to-private-NIC path and potentially different subnet and NIC NSG filtering. The comprehensive private-path diagnostic in the selected answer is more precise.

Question 664

An Azure VM sends HTTPS data across a supported IPsec site-to-site VPN. Small requests and TCP handshakes succeed, but large HTTPS responses hang; packet tests with the Don't Fragment flag fail at sizes that previously passed on the local VNet. The VPN firewall discards ICMP Fragmentation Needed messages. DNS and the destination TCP listener work. What should network operations investigate and correct first?

  1. Check path MTU discovery and VPN encapsulation overhead, permit appropriate ICMP feedback, and tune supported tunnel MTU or TCP MSS settings after measuring the path.
  2. Raise the source NSG's general allow priority, assuming an approved TCP 443 flow fails only when its payload becomes large because of Azure RBAC.
  3. Enable gateway transit on an unrelated peering connection, even though the existing IPsec VPN is established and small packets successfully traverse it.
  4. Change the destination's private DNS A record to a different name, although the same resolved endpoint accepts small HTTPS requests.

Explanation

Correct Answer

A:

VPN encryption adds headers that lower the effective packet payload budget. Blocking ICMP Fragmentation Needed can break PMTUD and create large-packet black holes even when TCP handshakes succeed. Measure DF packet sizes, evaluate fragmentation and tune MSS/MTU rather than changing identity permissions.

Incorrect Answers

B:

NSG rule priority determines whether the permitted connection can pass according to header properties; the stated existing TCP connection and small application packets work. RBAC and a broader NSG allow rule do not correct an encapsulation-related path MTU black hole.

C:

Gateway transit concerns connectivity through a peered VNet's gateway. The identified VPN path already carries small packets successfully, so changing an unrelated peering topology does not explain the payload-size threshold or blocked PMTUD messages.

D:

The destination FQDN already resolves and the same TCP server responds to small requests. Changing DNS names could redirect traffic but would not repair fragmentation and TCP MSS handling along the established VPN path.

Question 665

Azure VNet `vnet-app` previously handed out DNS server 10.2.0.5 via its DHCP configuration. After a planned migration, its VNet DNS server property now correctly lists new reachable resolver 10.2.0.4. VM `app01` has not renewed its DHCP lease and still shows 10.2.0.5 in the guest adapter settings. FQDN queries from `app01` fail even though queries to 10.2.0.4 succeed. Which action should the operator take?

  1. Renew the VM's DHCP lease (or use a supported restart procedure), verify its effective DNS server settings now reference 10.2.0.4, and retest the hostname.
  2. Flush only the local DNS response cache without renewing DHCP; assume the old configured resolver address automatically changes to the new one.
  3. Create a new NSG inbound TCP 443 rule for the application, even though name resolution fails before a destination IP address is chosen.
  4. Modify the VM's persistent guest network adapter DNS IP manually and ignore the centrally configured VNet DNS and DHCP settings for all future Azure service-heal operations.

Explanation

Correct Answer

A:

Microsoft documents that Azure VNet DNS changes require a DHCP lease renewal on affected VMs to apply new settings. After the lease updates the guest resolver, retest DNS traffic to the reachable new server before investigating the application.

Incorrect Answers

B:

Flushing cached answers clears prior responses but doesn't change the DNS server address delivered by an earlier DHCP lease. The VM would continue querying 10.2.0.5 until its actual resolver settings update.

C:

An NSG allow for application HTTPS governs network traffic after the client has resolved a destination; it cannot supply a working DNS resolver when the guest still points at a retired server.

D:

Directly hardcoding the guest resolver can be overwritten when Azure replaces its virtual NIC or performs service healing. The durable configuration belongs at the appropriate VNet/NIC DNS settings, followed by DHCP refresh.

Question 666

VM `app01` (10.8.1.7) opens an outbound TCP connection from ephemeral source port 51624 to backend `api01` (10.8.2.9) on destination port 8443. Routes and the destination VM's inbound NSG already allow this path. The source subnet NSG has an outbound Allow at priority 200 with source port 8443 and destination port Any, followed by a matching outbound Deny at priority 300. New connections fail. Which precise NSG fix permits only this approved application flow?

  1. Add an inbound Allow on the source subnet for TCP 8443 from the Internet; leave the outbound rule and its source-port filter unchanged.
  2. Change the API listener from destination port 8443 to ephemeral client source port 51624 so the existing source-port filter matches.
  3. Change the outbound Allow to source port Any and destination TCP port 8443, with the approved IP prefixes, retaining priority 200 ahead of the Deny.
  4. Change only the outbound Allow priority from 200 to 100 while keeping source port 8443 and destination port Any.

Explanation

Correct Answer

C:

NSG rules match protocol, direction, source address and port, and destination address and port. A client connection from source port 51624 to destination port 8443 does not match an Allow whose source-port field is 8443; using source port Any and destination TCP 8443 with scoped addresses permits the intended flow before priority-300 Deny.

Incorrect Answers

A:

The VM initiates the connection outbound, so an inbound rule on the originating subnet is not the missing admission rule. It would also unnecessarily expose inbound 8443 and still leave the outbound source-port mismatch in place.

B:

51624 is the ephemeral source port chosen by the client for this connection, not the application listener on the server. Reconfiguring the backend to listen on it would not make the source subnet rule match this packet and would disrupt the approved service port.

D:

Lowering the Allow priority number makes it evaluate earlier, but it still fails the complete five-tuple match because the actual source port is 51624, not 8443. The flow continues to the matching Deny; correcting the port fields, not priority alone, is required.

Question 667

An admin sees packets denied by NSG rule but cannot find the source assignment. What should the administrator do to resolve this specific case?

  1. Check firewall rules and return route, not just subnet NSG.
  2. Inspect effective routes, peering traffic settings and NSG permissions.
  3. Test private route and effective NSG policy plus the guest RDP listener and firewall, rather than attach a public IP.
  4. Inspect effective security rules and the VM NIC/subnet NSG associations to identify where the restriction originates.

Explanation

Correct Answer

D:

Effective security rules merge the security group rules inherited from a VM NIC and its subnet, with applicable priorities and directions. Inspect those effective rules and NSG associations to locate which assignment is actually denying the packet.

Incorrect Answers

A:

Inspecting guest or network firewall rules and return paths is useful after identifying a firewall-driven traffic drop. Here Azure has explicitly reported an NSG rule denying packets, and the question is which NSG assignment produced the rule. Examine the effective security rules and NSGs attached at the NIC and subnet, not unrelated firewall rules first.

B:

Effective route and NSG checks identify the Azure path and policy; they do not correct a broken DNS resolver or private host listener automatically.

C:

This alternative applies when a VM has no public IP, its corporate VPN is connected, but RDP to the private NIC address times out. An admin sees packets denied by NSG rule but cannot find the source assignment. It targets a different operational condition; the relevant administrative action is to inspect effective security rules and the VM NIC/subnet NSG associations to identify where the restriction originates. Using the alternative would not fulfill the specified requirement.

Question 668

Traffic from a VM reaches an Azure Firewall network virtual appliance, and its logs show an explicit deny for destination TCP 1433; the subnet and NIC NSG checks permit the flow. What should be investigated?

  1. The Azure Firewall rule collection/network rule evaluation and an approved return route for the flow.
  2. Assign Azure subscription Owner to the VM managed identity to bypass a firewall deny.
  3. Remove the application database from its VNet and expose a public IP.
  4. Change only the Blob Storage access tier, which controls TCP 1433 firewall admission.

Explanation

Correct Answer

A:

An explicit Azure Firewall deny is a firewall-policy decision; verify rule matching, destination, ports and reply routing rather than altering already-permitted NSGs.

Incorrect Answers

B:

Management-plane RBAC does not override packet-filter policy enforcement by the firewall.

C:

Internet-exposing the database is unnecessary and violates the intended private network boundary.

D:

Blob storage tiers do not configure TCP network security policies for the database flow.

Question 669

Two spokes are peered only to a hub VNet. A network virtual appliance in the hub is already configured to forward between the spokes, and effective user-defined routes on both spoke subnets point to its private IP. Security rules permit the intended traffic, but the spoke peerings do not allow receipt of forwarded traffic. The team must keep all spoke-to-spoke traffic inspected by the hub appliance. What setting must be corrected?

  1. Enable remote VPN gateway usage on each spoke regardless of whether the hub contains a gateway.
  2. Enable Allow forwarded traffic on the relevant peering directions so the spokes can receive packets forwarded by the hub appliance.
  3. Remove the route tables and peer the two spokes directly to each other, bypassing the hub appliance.
  4. Enable only Allow virtual network access on the peerings and assume it automatically allows forwarded third-party traffic.

Explanation

Correct Answer

B:

Azure VNet peering distinguishes normal direct VNet access from traffic forwarded by an intermediary appliance. In this case the hub NVA, route tables and relevant NSG permissions already exist, but peering settings prevent the destination spoke from receiving packets forwarded through the hub. Enabling Allow forwarded traffic in the appropriate peering direction addresses that specific missing permission while preserving required NVA inspection. It does not create routes or an NVA on its own, which is why the scenario explicitly establishes those components beforehand.

Incorrect Answers

A:

Remote gateway settings are for gateway or route-server transit, not permission for packets that an already deployed NVA forwards across a peering. The scenario states that the routed hub appliance, its UDR next hops and security controls are correctly configured. Adding gateway-transit settings would not address the disabled forwarded-traffic permission and might introduce unrelated constraints or dependencies.

C:

Direct spoke-to-spoke peering could create another connectivity path, but it would bypass the mandatory hub NVA inspection design. The owner requires the routed hub topology to remain in use, and current route tables already send traffic to that appliance. Replacing the topology instead of correcting forwarded-traffic settings undermines the security requirement and does not fix the existing path.

D:

Allow virtual network access governs ordinary traffic between the directly peered VNets; receiving packets forwarded by an NVA from another VNet is controlled separately. Microsoft notes that Allow forwarded traffic is not enabled by default and must be selected where this service-chaining pattern requires it. Simply keeping normal peering access enabled cannot satisfy the stated NVA forwarded-packet scenario.

Question 670

A route-based Azure VPN Gateway `VpnGw2` connects an Azure VNet `10.0.1.0/24` to a branch network that independently also uses `10.0.1.0/24`. The supported IPsec connection is established, but route matching cannot distinguish the two address spaces. The organization cannot renumber either network and has reserved distinct unused translated /24 ranges for both sides. Which gateway configuration resolves the overlap on that connection?

  1. Add only an IngressSNAT rule for the branch and keep the Azure VNet using its original overlapping 10.0.1.0/24 on the VPN connection.
  2. Add only an EgressSNAT rule for the Azure VNet and leave the branch's overlapping 10.0.1.0/24 unmodified on that connection.
  3. Enable BGP route translation while leaving the original on-premises and Azure address spaces overlapping and without any NAT mappings.
  4. Create appropriate nonoverlapping IngressSNAT and EgressSNAT mappings for the branch and Azure VNet respectively, associate them with the supported site-to-site IPsec connection and adjust routing or BGP translation where applicable.

Explanation

Correct Answer

D:

Azure VPN Gateway NAT supports route-based IPsec cross-premises connections on VpnGw2 and compatible SKUs. For overlap between the VNet and branch, ingress and egress SNAT use separate nonconflicting external mappings; link the rules to the intended connection and check translated routes or BGP settings as appropriate.

Incorrect Answers

A:

IngressSNAT maps the on-premises side into an unambiguous translated range. With the Azure VNet still using the same original prefix on that connection, the scenario continues to contain an overlapping local-versus-remote network space requiring separate egress mapping.

B:

EgressSNAT gives the Azure VNet a translated representation for the branch, but on-premises traffic still advertises the identical unmodified prefix. Because both sides use the same original /24, Microsoft documents configuring both sides' translation on that VPN connection.

C:

BGP route translation advertises already configured post-NAT prefixes as applicable. Without the underlying NAT mapping rules it does not translate packet addresses or solve the overlapping 10.0.1.0/24 endpoint prefixes.