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 63

Question 620

HubNet is peered to SpokeA and SpokeB; the spokes have no direct peering or hub forwarding configuration. Why is SpokeA unable to reach SpokeB privately by default?

  1. Peering is nontransitive; configure supported spoke-to-spoke routing via an NVA/hub or an explicit direct peering.
  2. Both spokes must have identically overlapping subnet CIDRs to forward traffic.
  3. Every peered VNet automatically becomes a transit router for all other peers.
  4. The hub requires a public IP on every backend VM for private routing.

Explanation

Correct Answer

A:

A hub-spoke design needs an explicit transit path because two separate peering relationships do not automatically create spoke-to-spoke forwarding.

Incorrect Answers

B:

Overlapping prefixes make route selection ambiguous and do not enable transit.

C:

Azure peering is not transitive by default; hub forwarding and route configuration are separate.

D:

Public VM IP addresses are not required to route private traffic via a supported NVA.

Question 621

A spoke VNet has no virtual network gateway of its own. Its applications must reach on-premises networks through the existing VPN gateway in peered hub VNet vnet-hub. Which TWO peering settings establish the supported gateway-transit relationship? Select TWO answers.

  1. Enable Use remote gateways on the spoke-to-hub peering after checking gateway eligibility.
  2. Enable Allow forwarded traffic alone on the spoke peering and leave gateway transit disabled.
  3. Deploy another VPN gateway into the spoke and also select Use remote gateways on the same spoke.
  4. Create an Azure public IP on every spoke VM and bypass the hub VPN gateway.
  5. Enable Allow gateway transit on the hub-to-spoke peering that owns the VPN gateway.

Explanation

Correct Answers

A:

The spoke can use the hub VPN gateway if its peering enables Use remote gateways and the hub side advertises that gateway for transit. This setting is configured on the spoke-to-hub peering, not on an unrelated VNet or storage account. The spoke must not already have its own gateway and should validate effective routes to the on-premises prefixes after the change. Enabling this option independently of its complementary hub setting is insufficient.

E:

The hub peering must permit its VPN gateway to be used by the peered spoke. Enabling Allow gateway transit on the hub-to-spoke relationship is the complement to Use remote gateways on the spoke side; neither setting on its own establishes both ends. Azure documents this paired configuration, and the hub must actually contain a compatible gateway. Check effective routes and security policies once both settings are saved.

Incorrect Answers

B:

Allow forwarded traffic controls whether peering accepts traffic forwarded by a remote network appliance or similar intermediary. It does not itself authorize a spoke to use the hub virtual network gateway. The requested design needs the gateway transit pairing, including the spoke-side remote-gateway choice. Forwarded-traffic settings may be relevant to other hub routing topologies, but cannot replace these gateway controls.

C:

A spoke virtual network cannot simultaneously use its own virtual network gateway and select another peered VNet’s remote gateway. Azure requires a single choice of local or remote gateway for that transit design. Installing a second gateway contradicts the case, which already has the central VPN gateway and specifically seeks shared transit.

D:

Public IPs on spoke VMs would not make those VMs use the hub-to-on-premises VPN gateway. They create an unrelated public connectivity path and may expose workloads needlessly. The requirement is private routing to on-premises prefixes through existing hub infrastructure. The appropriate controls are peering gateway-transit settings and the corresponding effective routes.

Question 622

App VMs in UK South and West Europe reside in distinct VNets with nonoverlapping CIDRs and must communicate privately over the Azure backbone. What should be configured?

  1. Attach both VMs to a UK South-only subnet.
  2. Configure supported global VNet peering between the regional VNets, including permitted traffic settings.
  3. Create one public DNS A record and assume it provides a private backbone route.
  4. Enable storage account object replication between regions as the VM network connection.

Explanation

Correct Answer

B:

Global VNet peering links eligible VNets across Azure regions for private IP connectivity on the Azure backbone.

Incorrect Answers

A:

A VNet subnet is regional and cannot contain VMs from a different region.

C:

Public DNS does not by itself create a private packet-forwarding path.

D:

Blob replication transfers object data; it does not connect VM subnet routes.

Question 623

An Azure VNet peering entry remains in the Initiated state after an engineer created only one side. What is the missing configuration?

  1. Increase the sending VM size to one with accelerated networking.
  2. Change the resource group names to match across subscriptions.
  3. Create the corresponding peering from the other VNet and verify the two links reach Connected state.
  4. Turn off HTTPS-only settings for any web app in the VNet.

Explanation

Correct Answer

C:

Both peering links are required for the relationship to become fully Connected.

Incorrect Answers

A:

VM compute sizing does not create the missing peering connection object.

B:

Peering works across resource groups and does not require identical resource-group names.

D:

App Service HTTP/TLS settings are unrelated to the VNet peering handshake.

Question 624

After expanding a peered VNet address space, a VM in its peer continues to use stale remote prefixes. What peering maintenance step is needed?

  1. Synchronize peering after the address-space change on the affected peering links, then verify effective routes.
  2. Regenerate the storage account access keys and retry the VM connection.
  3. Switch the VNet to a public IP allocation SKU.
  4. Set every NIC private IP address to the remote subnet network address.

Explanation

Correct Answer

A:

Azure peering can require address-space synchronization after prefix updates so peer routes reflect the new ranges.

Incorrect Answers

B:

Storage credentials do not update virtual network routing prefixes.

C:

Public IP SKU controls internet IP resources, not peering address-space sync.

D:

Network addresses cannot be assigned to Azure NICs, and static assignments would not sync the peering.

Question 625

Peering between two VNets is Connected but an application TCP flow is denied by a subnet NSG. What is the correct administrative fix?

  1. Review and adjust the relevant source/destination NSG rules for the precise flow while retaining the required peering.
  2. Change the Azure billing tag CostCenter to allow the TCP port.
  3. Delete all peering links and assume NSGs will stop filtering traffic.
  4. Grant Azure Reader to the VM guest account as a substitute for packet filtering.

Explanation

Correct Answer

A:

Peering routes packets between VNets but each associated NSG still evaluates traffic by direction, prefix, protocol and port.

Incorrect Answers

B:

Tags affect metadata and governance, not security-rule enforcement.

C:

Deleting peering removes the private route and does not solve an NSG deny for an active connection.

D:

Management-plane Reader access does not grant TCP connectivity through NSG rules.

Question 626

Two partner VNets use overlapping private CIDRs. The project cannot renumber immediately but needs a proposed connectivity design. Which statement about DIRECT Azure VNet peering is correct?

  1. Switch the peering to an IPv6 public IP and overlap is no longer relevant.
  2. Allow forwarded traffic in both peers and identical IPv4 prefixes become valid.
  3. Create a DNS zone link to permit peering with duplicate CIDRs.
  4. Direct peering requires nonoverlapping CIDRs; evaluate supported VPN/NVA translation or an address redesign instead.

Explanation

Correct Answer

D:

An overlapping address plan prevents direct peering; translation where supported or renumbering is necessary.

Incorrect Answers

A:

An IPv6 public address does not solve two overlapping private IPv4 VNet address ranges.

B:

Forwarded-traffic permission does not eliminate peering address overlap validation.

C:

DNS zone links resolve names and cannot make conflicting IP prefixes routable through direct peering.

Question 627

Two nonoverlapping Azure virtual networks reside in different subscriptions under different Microsoft Entra tenants. Both organizations authorize private connectivity, but an architect claims peering is categorically impossible between different tenants. Which assessment is correct?

  1. Cross-tenant Azure virtual network peering is impossible, even if both subscriptions are authorized to establish it.
  2. Azure VNet peering supports different subscriptions and Microsoft Entra tenants when both sides grant required permissions and create compatible peering links.
  3. Changing both VNet address spaces to the same CIDR is mandatory before cross-tenant peering is permitted.
  4. Publishing an Azure public DNS CNAME between tenants automatically establishes the peering data-plane connection.

Explanation

Correct Answer

B:

VNet peering can be established across different subscriptions and Entra tenants when the two authorized parties configure the peering relationships and satisfy compatible address-space and access requirements.

Incorrect Answers

A:

Microsoft supports VNet peering between subscriptions belonging to different Entra tenants. Tenant boundaries require deliberate access and link setup, not a blanket prohibition.

C:

Overlapping address spaces block ordinary VNet peering; deliberately making CIDRs identical would prevent rather than enable the desired private route.

D:

A public DNS alias resolves names, but neither creates a virtual-network peering resource nor grants the Azure permissions needed by participating tenants.

Question 628

Two business VNets are peered, but finance must block TCP 443 between specified subnets while allowing other approved communication. Which control implements that selective deny?

  1. Delete the entire VNet and all subnets to remove the flow.
  2. Rename the peering connection and keep default traffic policies.
  3. Use appropriately scoped NSG or central firewall rules matching source, destination and port.
  4. Change the finance app’s DNS label without changing security rules.

Explanation

Correct Answer

C:

NSG and firewall rules can target the exact port/prefix pairs even while peering remains connected.

Incorrect Answers

A:

Deleting a VNet destroys unrelated connectivity and exceeds the targeted requirement.

B:

Peering name is descriptive metadata, not a transport-layer authorization rule.

D:

A DNS label cannot enforce selective TCP traffic restrictions.

Question 629

An administrator intends to remove the only peering between two regional application VNets. What should happen before deletion to avoid an unintended outage?

  1. Validate application dependencies and establish/test an alternate private path or coordinated cutover.
  2. Change each VM public IP domain label so private peering traffic persists.
  3. Set the peering status to Disconnected but assume active connections remain routable indefinitely.
  4. Disable the Azure Monitor workspace to prevent impact alerts.

Explanation

Correct Answer

A:

Peering removal withdraws the direct private VNet connection; dependent application flows need an alternate tested path.

Incorrect Answers

B:

Public IP DNS labels do not replace private peering reachability.

C:

A disconnected peering does not guarantee existing private routes or packet delivery.

D:

Suppressing monitoring hides effects without preserving application connectivity.

Question 630

VNets `vnet-app` and `vnet-data` have an established peering. An app VM in vnet-app now fails to open HTTPS on a data VM's private IP in vnet-data. Network Watcher reports the two VNet address spaces and effective VM routes as valid, and the applicable NSGs already allow TCP/443. Inspection shows `allowVirtualNetworkAccess = false` on the vnet-app-to-vnet-data peering, while the reverse peering permits virtual network access. Neither VNet uses a gateway or transit NVA for this private flow. What change addresses the observed block?

  1. Enable virtual network access on the vnet-app-to-vnet-data peering and verify the reciprocal peering and effective private path remain permitted.
  2. Enable `allowForwardedTraffic` only, although this connection is direct VM-originated traffic and not a third-party NVA forwarding path.
  3. Enable `allowGatewayTransit` on the peering, even though both VMs exchange traffic directly through peering and require no gateway transit.
  4. Replace the private route with a `Virtual network gateway` next hop to force the same-VNet-address-space traffic into an absent VPN gateway.

Explanation

Correct Answer

A:

Allow virtual network access controls whether VM traffic from this peered VNet can reach VM IPs in the remote peered address space. It is explicitly disabled on the source peering, so enabling it restores that prerequisite, subject to the already validated reverse setting, routing and NSG controls.

Incorrect Answers

B:

Allow forwarded traffic concerns packets forwarded into the peering by a network virtual appliance and does not replace disabled direct VNet access. The app VM is the original sender, not an NVA forwarding someone else's traffic.

C:

Gateway transit concerns using a gateway in a remote peered VNet. No gateway is involved in this direct east-west connection, and this flag does not override `allowVirtualNetworkAccess = false`.

D:

A route to a nonexistent VPN gateway is not a valid repair. The effective VNet peering route is already present; only the peering's disabled virtual network access permission is implicated.