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 66

Question 650

A security team requires general Internet-bound traffic from Azure VM subnet `sn-app` to traverse Azure Firewall at private IP `10.0.10.4`. Firewall policy, egress translation and return routing are separately configured. No more-specific UDR overrides are in scope. Which subnet route-table configuration selects the required next hop?

  1. Associate a 0.0.0.0/0 route on sn-app whose next hop is Virtual appliance and next-hop IP is 10.0.10.4.
  2. Associate a 0.0.0.0/0 route on sn-app whose next hop is Internet to keep application traffic outside the firewall.
  3. Associate a 0.0.0.0/0 route whose next hop is Virtual network gateway, sending general egress toward the VPN gateway instead of the Azure Firewall IP.
  4. Associate a 0.0.0.0/0 route whose next hop is None, intentionally discarding general egress packets before they reach the firewall.

Explanation

Correct Answer

A:

A default UDR with Virtual appliance and the firewall private IP routes otherwise unmatched destinations to the specified Azure Firewall hop for this subnet. Associating the route table to sn-app applies the routing decision; firewall filtering, translation and return routing are independent prerequisites already provided in the scenario.

Incorrect Answers

B:

Internet selects Azure Internet egress rather than the specified firewall appliance next hop. It is suitable for a subnet explicitly exempted from VPN forced tunneling, not for one whose policy requires inspection through 10.0.10.4.

C:

Virtual network gateway directs the route toward a VPN/ExpressRoute gateway, not the private IP of the Azure Firewall instance. It could implement a different on-premises forced-tunnel architecture but does not satisfy this exact firewall next-hop requirement.

D:

None is the supported black-hole next hop for a UDR and drops matching packets. It would prevent the outbound application traffic from reaching Azure Firewall and therefore cannot implement inspected Internet access.

Question 651

A VM in a peered VNet has a system peering route, but traffic to a remote prefix unexpectedly reaches an NVA. Which routing check explains the behavior?

  1. Assume system peering routes always take priority over all matching UDRs.
  2. Check only DNS propagation and ignore effective routes.
  3. Remove the peering, which will guarantee the system route is selected.
  4. Inspect the effective route table, longest-prefix match and route source/priority to find the overriding UDR.

Explanation

Correct Answer

D:

Effective routes show the winning next hop and source for the exact destination prefix.

Incorrect Answers

A:

A matching user route can override a system route when the route selection rules permit it.

B:

DNS only resolves destination names and cannot prove why an IP packet chose an NVA next hop.

C:

Removing peering eliminates the system peering route and does not solve an unexpected custom route.

Question 652

An Azure VNet receives a `0.0.0.0/0` forced-tunnel default route from its site-to-site VPN gateway over BGP. Security approves only subnet `frontend` to send general Internet traffic directly through its already configured NAT Gateway; subnet `backend` must remain forced through the VPN. Both must still route private branch prefix `10.20.0.0/16` over VPN. Which routing change meets those constraints without disabling private-route propagation?

  1. Disable gateway route propagation on the shared route table for both subnets, expecting all branch routes to remain and only frontend Internet traffic to change.
  2. Add a 0.0.0.0/0 UDR with Virtual network gateway next hop to frontend, reinforcing the already learned forced-tunnel default.
  3. Associate only with frontend a route table containing a 0.0.0.0/0 UDR whose next hop is Internet; keep BGP propagation and the specific branch route in effect.
  4. Send 10.20.0.0/16 traffic to the Internet next hop and leave the inherited 0.0.0.0/0 VPN route untouched on frontend.

Explanation

Correct Answer

C:

A UDR at 0.0.0.0/0 has precedence over an equally broad BGP-learned default, selecting the Internet next hop on only the frontend subnet. More-specific 10.20.0.0/16 branch routes can remain gateway-directed and backend retains its inherited VPN default. The preconfigured NAT Gateway supplies the frontend outbound translation.

Incorrect Answers

A:

Globally disabling BGP propagation would remove learned gateway prefixes and may break the required private branch path for both subnets. The requirement is a subnet-local Internet exception, not turning off VPN route learning.

B:

A default UDR pointing at Virtual network gateway continues sending Internet-bound packets toward the VPN, so it does not make frontend egress directly via Azure NAT Gateway. The learned default already has that behavior.

D:

Changing the branch-specific prefix toward Internet breaks the explicit requirement that private on-premises traffic use the VPN. It also leaves the 0.0.0.0/0 learned forced-tunnel default selected for other destinations, so frontend Internet traffic is not exempted.

Question 653

Only workloads in SubnetA should forward traffic for 10.70.0.0/16 through an NVA, while SubnetB retains system routes. Where should the custom route table be associated?

  1. To the top-level Azure subscription and every VNet automatically.
  2. To the entire parent resource group, which forces all its subnets.
  3. To a public IP address that shares SubnetA’s name.
  4. To SubnetA only, with the intended destination and Virtual appliance route.

Explanation

Correct Answer

D:

Subnet-specific association limits the custom routing effect to the targeted subnet.

Incorrect Answers

A:

Route tables are associated with subnets, not broadly with a subscription’s VNets.

B:

Resource-group membership does not attach UDRs to every subnet it contains.

C:

Public IP association does not configure private subnet route-table behavior.

Question 654

A VM cannot reach a Storage Blob private endpoint after a route table change. DNS resolves the blob hostname to a private endpoint IP. What should be checked before changing DNS?

  1. Delete the private DNS A record to force a public endpoint.
  2. Inspect effective routes, private-endpoint network policy configuration and firewall/NSG behavior for the /32 target.
  3. Change the managed disk SKU for the VM.
  4. Enable anonymous Blob access and assume a denied network route is bypassed.

Explanation

Correct Answer

B:

The private endpoint has a private IP and route/network-policy interactions can affect forwarding to it even when DNS is correct.

Incorrect Answers

A:

The hostname already resolves to the private endpoint; deleting its mapping hides rather than resolves the routing failure.

C:

Disk performance tiers do not determine the private endpoint route and filtering decision.

D:

Blob authorization cannot override blocked Layer-3 connectivity to the target private IP.

Question 655

A site-to-site VPN tunnel is Connected and its Azure VPN gateway continues learning branch prefix `10.44.0.0/16`. After an administrator enables `Disable BGP route propagation` on route table `rt-app` associated with subnet `sn-app`, a VM’s effective routes no longer include that branch prefix and private connectivity fails. There is no specific UDR for it. What directly explains and fixes the routing failure?

  1. Add a 0.0.0.0/0 UDR with next hop Internet; the gateway-learned 10.44.0.0/16 branch prefix will then automatically reappear.
  2. Replace the working VPN connection shared key, even though the tunnel is connected and the gateway still learns the branch prefix.
  3. Add a permissive inbound NSG rule for 10.44.0.0/16, assuming NSG approval supplies the missing next-hop route.
  4. Reenable gateway route propagation on rt-app and confirm 10.44.0.0/16 appears in effective routes, or install a deliberately correct specific route if propagation must stay disabled.

Explanation

Correct Answer

D:

Disable BGP route propagation on a subnet-associated route table suppresses learned gateway routes from VM effective route tables. Reenabling it restores the expected branch prefix; a supported, intentionally configured specific UDR is an alternative if route propagation is deliberately disabled.

Incorrect Answers

A:

An Internet default route does not restore the disabled BGP-propagated 10.44.0.0/16 gateway route. It may send otherwise unmatched private branch packets to Internet rather than the S2S VPN, leaving the actual route loss unresolved.

B:

The tunnel already operates and the gateway continues learning the prefix. Rotating the shared key addresses IPsec authentication, not the explicit route-table control that suppresses propagation into this subnet.

C:

NSGs filter traffic according to security rules but cannot add a missing destination prefix or choose the VPN gateway next hop. A permissive filter would not restore the subnet’s route to 10.44.0.0/16.

Question 656

Subnet `app` has an associated route table sending 10.90.0.0/16 to the private IP of VM-based firewall `nva01` in a separate subnet. Network Watcher confirms the appliance is the selected next hop. The relevant NSGs allow the traffic, and the appliance OS/firewall already has routing enabled. Packets destined for 10.90.4.20 reach the appliance but are not forwarded. Inspection shows `enableIPForwarding` is false on the appliance network interface. Which Azure change directly addresses the remaining fault?

  1. Change the source subnet route next-hop type from `Virtual appliance` to `Virtual network` and keep using the same appliance address.
  2. Enable accelerated networking on the appliance NIC, since accelerated networking automatically authorizes transit packets.
  3. Enable virtual network gateway route propagation on the source route table even though the UDR already selects the appliance and no gateway is involved.
  4. Enable IP forwarding on the appliance network interface and confirm the previously configured guest forwarding path remains in effect.

Explanation

Correct Answer

D:

Azure IP forwarding must be enabled on each NIC used by a VM-based network virtual appliance to handle transit packets whose destination is not the appliance itself. Guest forwarding is already enabled by premise, so enabling the disabled Azure NIC setting directly removes this identified forwarding restriction.

Incorrect Answers

A:

Changing a UDR next-hop type to `Virtual network` does not keep the explicit NVA next-hop IP and would remove the intended inspection path. The source already selects the correct appliance, so route selection is not the missing prerequisite.

B:

Accelerated networking is a NIC performance feature and does not substitute for Azure NIC IP forwarding. A VM-based router must be permitted to receive and send packets with addresses other than those assigned to its own interface.

C:

Gateway propagation controls learning virtual network gateway routes into effective route tables. The chosen UDR already directs the flow to `nva01`; adjusting gateway propagation cannot enable the appliance NIC to forward transit packets.

Question 657

A subnet route table points all outbound traffic to an NVA VM that has been deallocated for maintenance. What design prevents a repeat outage?

  1. Change the Azure DNS TTL to one second and expect the NVA route to recover.
  2. Enable a resource lock on the deallocated NVA VM.
  3. Implement supported high availability/failover for the appliance path and keep subnet routes pointing at a working next hop.
  4. Add an additional NSG allow rule while leaving the next-hop VM offline.

Explanation

Correct Answer

C:

An HA or failover route plan ensures the chosen next hop remains functional when one appliance fails.

Incorrect Answers

A:

DNS TTL does not bring an unavailable virtual appliance online or redirect a static next hop.

B:

A lock controls resource deletion and does not supply a healthy packet-forwarding appliance.

D:

An NSG permit cannot cause packets to be forwarded by an offline NVA.

Question 658

After adding a 0.0.0.0/0 UDR to a third-party NVA, an app stops reaching an Azure Storage public endpoint. What should the operator investigate?

  1. Assume any route to 0.0.0.0/0 affects only non-Azure internet hosts.
  2. Disable resource logging and expect routing to recover.
  3. Change the Storage account encryption key without checking the egress appliance.
  4. Examine UDR selection, appliance egress/NAT and service-endpoint/private-endpoint routes or exceptions as appropriate.

Explanation

Correct Answer

D:

Azure service reachability depends on effective routing and the appliance/network policy as well as any relevant service or private endpoints.

Incorrect Answers

A:

A default UDR may capture routes toward Azure public endpoints when no more-specific service route applies.

B:

Logging switches do not repair an unusable forced-tunnel path.

C:

Data-at-rest encryption does not define the outbound IP route through an NVA.

Question 659

After a change to a subnet NSG, two VMs in the same VNet can no longer communicate over TCP 8443. What is the first evidence-based security check?

  1. Examine both NIC/subnet effective NSG rules, traffic direction and the source/destination port before editing them.
  2. Change the VNet resource name to the default value.
  3. Recreate both managed VM data disks.
  4. Create a public IP on each VM to bypass their private NSG rules.

Explanation

Correct Answer

A:

The aggregate effective security rules reveal applicable subnet/NIC policies that could deny the precise flow.

Incorrect Answers

B:

Renaming a VNet does not change NSG evaluation for a packet.

C:

Disk recreation cannot correct subnet packet filtering and risks data loss.

D:

Public IPs do not disable effective NSG restrictions and add exposure.

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.