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 62

Question 610

A VM application must retain a specified private address on its NIC inside the subnet throughout normal restarts. Where should that static allocation be made?

  1. Set a public IP DNS label equal to the desired private IPv4 address.
  2. Change the VM operating-system subnet mask while leaving Azure NIC dynamic.
  3. Configure static private IP allocation on the Azure NIC IP configuration using an available address in its subnet.
  4. Configure a new Azure billing tag named PrivateIP.

Explanation

Correct Answer

C:

Azure NIC private-IP allocation settings own persistent private addressing for the VM resource.

Incorrect Answers

A:

A public DNS label names a public resource; it is not the private NIC assignment.

B:

Hardcoding guest address settings without matching Azure NIC allocation risks an address mismatch.

D:

Tags are metadata and do not program the Azure private-IP allocation state.

Question 611

Production VNet vnet-sales has subnet sn-app at 10.16.8.0/24. Operations proposes shrinking it to 10.16.8.0/25 without redeploying the connected workloads. NICs and private endpoints currently hold addresses including 10.16.8.35 and 10.16.8.102. What should be verified before making the change?

  1. Delegate sn-app to an unrelated Azure PaaS service to override existing assigned addresses.
  2. Convert every NIC to a static private-IP assignment and skip validation of the smaller address prefix.
  3. Confirm that every allocated address remains inside 10.16.8.0/25, and that Azure subnet-resize conditions and address capacity are met.
  4. Create a second overlapping subnet with prefix 10.16.8.0/25 while the original subnet is still attached.

Explanation

Correct Answer

C:

Current Azure troubleshooting guidance allows resizing a subnet containing active resources only when the new range accommodates all existing assigned addresses. The listed .35 and .102 addresses fit within the proposed /25, but they do not prove that other NICs, private endpoints or service allocations also fit. The administrator should inventory assigned addresses, check subnet capacity including Azure-reserved addresses, and validate resource-specific constraints before committing the change. Otherwise the update can fail or disrupt allocation.

Incorrect Answers

A:

Subnet delegation grants supported service-specific control over a subnet, not permission to ignore allocated IP addresses. It can introduce additional restrictions on workloads already deployed there. The requested action is an address-prefix shrink; attaching an unrelated delegation would not validate or preserve the existing private IP assignments.

B:

A static private address still must lie within the subnet prefix and must not conflict with reserved or allocated addresses. Converting dynamic addresses to static does not make an out-of-range endpoint valid. The administrator must examine the actual assigned addresses and the candidate prefix before attempting a resize.

D:

Azure subnets within one virtual network cannot overlap. The proposed smaller prefix lies entirely inside the currently configured /24 and therefore cannot coexist as another subnet. Creating a duplicate address space would fail validation rather than shrink the existing subnet with its attached workloads.

Question 612

A VNet uses 10.20.0.0/24. The prefixes 10.20.0.0/26 and 10.20.0.64/26 are occupied by application subnets, while 10.20.0.128/26 is reserved for the database tier. The remaining address block is free. The team must add a dedicated Azure Bastion Standard host in this VNet without changing existing allocations. Which subnet reservation is valid?

  1. Reserve 10.20.0.192/26 as the dedicated AzureBastionSubnet.
  2. Rename the occupied 10.20.0.0/26 application subnet to AzureBastionSubnet and retain its existing VMs.
  3. Create AzureBastionSubnet using 10.20.0.224/27 because a 32-address subnet always meets current Standard SKU requirements.
  4. Reserve 10.20.0.192/26 as GatewaySubnet and deploy Bastion there alongside any VPN gateway.

Explanation

Correct Answer

A:

A /24 divides cleanly into four nonoverlapping /26 prefixes: .0/26, .64/26, .128/26 and .192/26. The first three are unavailable under the given allocations, leaving 10.20.0.192/26 for the new host. Azure Bastion Standard requires a dedicated subnet named exactly AzureBastionSubnet with a /26 or larger address space for new deployments. Reserving the free /26 under that exact name respects both Azure Bastion requirements and the specified VNet address plan without moving the existing application or database subnet assignments.

Incorrect Answers

B:

An application subnet already contains resources, so renaming it does not create the dedicated empty subnet required for the Bastion host. The chosen address range is also already allocated to the application tier, and the requirement explicitly forbids changing existing allocations. Bastion needs its own correctly named and appropriately sized subnet, not a repurposed workload subnet containing VMs.

C:

The prefix 10.20.0.224/27 is a valid CIDR block inside the unused /26, but a /27 is smaller than the /26 minimum for a new Azure Bastion Standard deployment. Microsoft documents /26 or larger for supported dedicated Bastion subnets created under current requirements. Subnet address mathematics alone does not establish eligibility for a managed service's reserved deployment subnet.

D:

GatewaySubnet is a reserved name used for virtual network gateways; it is not interchangeable with AzureBastionSubnet. Even though 10.20.0.192/26 has enough address space, the wrong reserved name and proposal to share it with a gateway would fail the Bastion-specific dedicated-subnet design. The correct network reservation is the free block with Azure Bastion's exact subnet name.

Question 613

An Azure managed service explicitly requires a subnet delegated to its provider and rejects a shared general-purpose subnet. Which change satisfies the deployment prerequisite?

  1. Add a CNAME record that points to the service hostname.
  2. Create or select a supported subnet and delegate it to the required Azure service, checking other subnet occupants.
  3. Give the managed service a public IP while keeping the prohibited delegation state.
  4. Enable VNet peering on both sides without configuring subnet service delegation.

Explanation

Correct Answer

B:

Azure subnet delegation authorizes the selected PaaS service to deploy the network resources it manages; incompatible occupants must be considered.

Incorrect Answers

A:

DNS aliases cannot establish service ownership of a subnet.

C:

A public IP does not fulfill an explicit subnet delegation requirement.

D:

Peering connects VNets and is independent of delegating a subnet to a PaaS resource type.

Question 614

A multihomed Azure VM has two NICs in different subnets. Network traffic works on one interface but not the other. What is the appropriate Azure network inventory to inspect?

  1. Inspect both NIC IP configurations, subnet membership, effective routes and NSGs for the failing traffic path.
  2. Change the default DNS name of the resource group.
  3. Assume all VM NICs share the primary NIC subnet and security policy.
  4. Increase the managed OS disk size to correct the secondary NIC routing.

Explanation

Correct Answer

A:

Multiple NICs can be attached to separate subnets and each path can have different security and routing controls.

Incorrect Answers

B:

Azure resource-group names do not determine packet forwarding across NICs.

C:

A secondary NIC does not automatically inherit the primary NIC subnet or effective route set.

D:

OS disk capacity is unrelated to the specific NIC/subnet traffic failure.

Question 615

Two service tiers live in two separately managed Azure VNets with nonoverlapping CIDRs. They need low-latency private connectivity without exposing workload VMs publicly. Which architecture is appropriate?

  1. Use direct VNet peering or another authorized private routed connection and apply the necessary traffic controls.
  2. Attach both VMs to the same subnet name without moving their VNets.
  3. Enable anonymous access on each workload storage account to enable private routing.
  4. Add matching DNS A records without creating any network path.

Explanation

Correct Answer

A:

Peering provides a private backbone path between two eligible VNets; NSGs/firewalls still apply.

Incorrect Answers

B:

A subnet is scoped to its own VNet and names alone cannot bridge two networks.

C:

Public storage permissions do not create inter-VNet private connectivity.

D:

DNS mapping resolves names, but private IP reachability still requires a network connection.

Question 616

An Azure VNet has a /24 address space and a new subnet requires an additional nonoverlapping /24. Which supported change avoids deleting the VNet?

  1. Overwrite the VNet CIDR with the same prefix and assume address capacity doubles.
  2. Set public IP allocation to Dynamic on existing private NICs.
  3. Add another nonoverlapping address-space prefix to the VNet, then create the subnet using available space.
  4. Add a management-group Reader role to every subnet user.

Explanation

Correct Answer

C:

A VNet can have multiple supported address prefixes; a distinct prefix enables an additional nonoverlapping subnet.

Incorrect Answers

A:

Reapplying an identical prefix adds no distinct private addresses.

B:

Public IP allocation does not expand the private address space of the VNet.

D:

Azure RBAC changes who can view resources, not the usable VNet CIDR inventory.

Question 617

An engineer creates a VNet with 10.50.0.0/16 and later discovers that an on-premises network reached through VPN uses the same CIDR. What must the hybrid network plan address?

  1. Apply an NSG allow rule and expect the overlapping addresses to route uniquely.
  2. Change only the Azure subscription name.
  3. Resolve the address overlap with a supported renumbering or translation design before relying on the hybrid route.
  4. Create a private DNS zone with the same suffix and ignore IP collisions.

Explanation

Correct Answer

C:

Overlapping prefixes cause route ambiguity and require an address plan or explicitly supported translation architecture.

Incorrect Answers

A:

NSGs filter packets but cannot disambiguate identical destination prefixes on two networks.

B:

Subscription display name changes are unrelated to Layer-3 address planning.

D:

DNS naming can map endpoints, but it does not eliminate underlying duplicate routed IP addresses.

Question 618

Two VNets in the same Azure region have nonoverlapping prefixes and need direct private IP access. What must the administrator configure to obtain connected peering?

  1. Only a custom route 0.0.0.0/0 to the internet in each subnet.
  2. A storage account private endpoint in both VNets with no peering.
  3. Compatible peering links from both VNets, with permitted VNet access and appropriate security rules.
  4. A resource-group-level DNS alias with no peering connection.

Explanation

Correct Answer

C:

Two-way peering establishes the direct backbone path between eligible VNets, subject to their policies.

Incorrect Answers

A:

A default internet route is not a direct VNet private connection.

B:

Storage private endpoints connect to specific PaaS resources and do not themselves peer two VNets.

D:

DNS aliases cannot substitute for VNet peering state and route reachability.

Question 619

Spoke VM app01 must send all TCP traffic for 10.40.0.0/16 to a firewall NVA at 10.10.1.4 in a peered hub VNet. Both VNet address spaces are nonoverlapping and peering allows normal VNet traffic. The NVA forwards packets from the spoke but the spoke currently sends 10.40.0.0/16 elsewhere. Which TWO additional controls must be configured? Select TWO answers.

  1. Associate a route table to the spoke source subnet with a 10.40.0.0/16 route whose next hop is Virtual appliance 10.10.1.4.
  2. Turn on a public IP address on the spoke VM so that it can bypass the private NVA.
  3. Enable gateway transit and Use remote gateways even though the hub uses an NVA rather than a VPN gateway.
  4. Permit forwarded traffic on the appropriate hub/spoke peering relationship so appliance-forwarded packets are accepted.
  5. Assign the Virtual Machine Contributor role to every user so network packet forwarding works automatically.

Explanation

Correct Answers

A:

A spoke route table with a matching destination prefix and Virtual appliance next hop directs the VM’s packets toward the hub NVA instead of the prior system or custom path. Associate the route table with the source subnet and check effective routes at the NIC to confirm selection. This is a routing change; merely allowing peering traffic does not create the necessary UDR or guarantee that traffic uses the firewall.

D:

Virtual network peering has a forwarded-traffic control for packets that a network virtual appliance forwards into a peered network. Enable the required setting for the relevant peering direction, consistent with the hub forwarding topology, while retaining the ordinary VNet access setting already present. This avoids assuming peering alone automatically handles appliance transit. Also check NVA IP forwarding and NSGs during validation; the two requested missing configuration controls are peering forwarding and a source-subnet UDR.

Incorrect Answers

B:

A public IP does not make a private 10.40.0.0/16 flow traverse the specified hub firewall. It changes how the VM can be reached publicly and risks unnecessary exposure. The design requires private peered-VNet forwarding through an NVA with suitable effective routes and security policies.

C:

Gateway transit settings share a virtual network gateway, such as a VPN gateway, with a peered VNet. The case uses a network virtual appliance, not a gateway-sharing requirement. Configuring remote-gateway settings would not install the needed custom destination route or authorize all NVA-forwarded packets. Use the peering forwarded-traffic setting with a UDR instead.

E:

Virtual Machine Contributor grants Azure control-plane rights to administer VM resources; it is not a data-plane routing or network packet-forwarding control. Giving broad administrative access to users would not change peering forwarding behavior or UDR selection. Configure route tables and allowed forwarded traffic instead.

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.