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 64

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.

Question 631

Nonoverlapping VNets in West Europe and East US are globally peered. A healthy service in East US uses a private frontend on an internal Standard Load Balancer. An engineer claims global VNet peering prevents all remote clients from using any internal Load Balancer frontend. Which statement correctly describes Azure support?

  1. Peering permits VM-to-VM private IP traffic, but it universally blocks the frontend IP of every internal Azure Load Balancer.
  2. Use a cross-region VPN gateway because global VNet peering cannot forward to a Standard internal Load Balancer frontend.
  3. Replace the internal Standard frontend with a public frontend; private frontend IPs cannot be reached across global peering.
  4. The Standard internal Load Balancer frontend is reachable across properly routed and permitted global VNet peering; the former Basic Load Balancer limitation does not apply to Standard.

Explanation

Correct Answer

D:

Global VNet peering supports access to private frontend IPs on Standard Load Balancers when peering, routing and security controls permit the traffic. The documented Basic SKU limitation is not a limitation of Standard internal Load Balancers.

Incorrect Answers

A:

Global peering does not universally block internal load balancers. Microsoft documents a limitation on Basic SKU frontend IPs across global peering, whereas Standard internal frontends can be reached when network routing and permissions are correct.

B:

A VPN gateway is not required solely because the destination is an internal Standard Load Balancer in a globally peered VNet. Global peering can carry the permitted private client traffic directly.

C:

Replacing the private frontend with a public one introduces an unnecessary internet-facing path. Standard internal Load Balancers support global VNet peering; check the network path and security controls instead.

Question 632

A single Azure VM must expose an approved TCP service on one stable IPv4 internet address. Which Azure public IP allocation is suitable?

  1. Use a storage account connection string as the VM’s internet endpoint.
  2. Allocate the IPv4 network address 10.0.0.0 to the VM NIC.
  3. Create a Standard static public IPv4 resource in the compatible region and associate it with the eligible NIC or frontend.
  4. Add a private DNS A record only and assume external clients can route to the private IP.

Explanation

Correct Answer

C:

Standard public IP provides a static internet-facing resource address when correctly associated and security rules permit traffic.

Incorrect Answers

A:

Storage account connection strings authorize storage access, not VM public endpoints.

B:

An RFC1918 network address is not a public routable VM endpoint.

D:

Private DNS resolution alone cannot make a private subnet address accessible to arbitrary internet clients.

Question 633

A database VM must have no direct internet-facing public IP but still be manageable securely by administrators. Which design satisfies the requirement?

  1. Attach a Standard public IP and allow RDP from 0.0.0.0/0.
  2. Publish the VM guest password in a private DNS record.
  3. Leave the VM NIC without a public IP and manage it over VPN/ExpressRoute or Azure Bastion with approved access.
  4. Enable anonymous registry pulls to make the guest reachable.

Explanation

Correct Answer

C:

Private-only NIC access plus a managed private path or Bastion supports administration without a VM public IP.

Incorrect Answers

A:

A direct public IP with an open management port violates the isolation requirement.

B:

DNS is not a secret store or remote-management channel.

D:

ACR permissions have no effect on inbound network exposure of a database VM.

Question 634

An internet-facing frontend must continue to use a reachable public IP if one availability zone fails in a supported Azure region. Which public-IP setting should be selected?

  1. A Basic public IP, which provides guaranteed zone resiliency.
  2. An IP from a different region with a matching subnet name.
  3. A Standard public IP configured as zone-redundant in an eligible region.
  4. A private address from the VNet gateway-reserved range.

Explanation

Correct Answer

C:

Zone-redundant Standard public IPs distribute frontend IP availability across zones in supported regions.

Incorrect Answers

A:

Basic public IP SKU is retired and did not provide the Standard zone-redundancy model.

B:

Regional Azure frontend public IPs must be compatible with their target regional services.

D:

Private reserved gateway addresses are not reachable internet endpoints.

Question 635

A team is about to create a new Standard static IPv4 public IP for an internet-facing Azure service. The approved connectivity design favors ISP-based Internet routing rather than keeping the path on Microsoft's global backbone as long as possible. The address has NOT been provisioned yet. Which action sets the intended public-IP routing behavior?

  1. Create the public IP with the default Microsoft network preference, then toggle it to Internet after the IP is assigned.
  2. Set the public IP availability zone to Zone-redundant; this automatically changes its routing preference to Internet.
  3. Add a public DNS name label to the public IP; DNS labels determine whether ISP routing is selected.
  4. Create the supported Standard IPv4 public IP with Routing preference set to Internet at creation time.

Explanation

Correct Answer

D:

The Internet routing preference is selectable when creating a supported Standard IPv4 public IP. This chooses the ISP-based route rather than the default Microsoft global network for eligible internet traffic, and the preference cannot later be changed on that IP.

Incorrect Answers

A:

The default is Microsoft-network routing, and the routing preference of an existing public IP cannot be changed after creation. The team must choose the preference before allocating the address.

B:

Zone redundancy affects how the IP survives an availability-zone outage, not whether traffic exits Azure over Microsoft-network or Internet routing preference. These are separate settings.

C:

A DNS name label supplies a DNS alias for the public IP and does not choose the routing network. It cannot replace the routing-preference property.

Question 636

Four Azure VMs in the same subscription and region require distinct static public IPv4 endpoints. An upstream partner can allowlist only one contiguous four-address range, and the addresses must remain reserved for the organization. What should the networking team provision?

  1. Create four unrelated Standard static public IPs and assume Azure allocates consecutive addresses.
  2. Reserve an eligible /30 Public IP Prefix, create four Standard static IPv4 resources from that prefix, and associate them with the VMs.
  3. Assign each VM a private address from a /30 VNet subnet and advertise that private block as internet-facing public space.
  4. Create DNS aliases for each VM and assume DNS creates a contiguous reserved set of public IPv4 addresses.

Explanation

Correct Answer

B:

An Azure Public IP Prefix reserves a contiguous address range within a region and subscription; a /30 prefix contains four IPv4 addresses. Supported Standard static public IP resources can be created from the range and individually associated with eligible NICs, satisfying both stable addressing and the single CIDR allowlist.

Incorrect Answers

A:

Unrelated static public IP resources remain reserved but Azure does not guarantee that independently allocated addresses form an adjacent CIDR range. The partner needs a known contiguous block, which requires reserving a public IP prefix.

C:

A private subnet assigns addresses routable within a VNet, not internet-routable public IP endpoints. Azure public-IP-prefix allocation is a separate resource, and a VNet /30 cannot be advertised as four public VM addresses.

D:

DNS maps names to existing addresses but does not reserve or allocate consecutive public IPv4 resources. The upstream firewall requires a contiguous address allocation independent of naming.

Question 637

An Azure web service requires IPv6 internet ingress in addition to IPv4 while its existing IPv4 path must continue. Which change is appropriate?

  1. Allocate an IPv4 address and change only DNS TTL to simulate IPv6.
  2. Configure supported dual-stack public IP resources/frontend and network rules for both IPv4 and IPv6.
  3. Assign the IPv6 loopback prefix ::1 to the Azure public interface.
  4. Enable a storage account private endpoint and claim it adds IPv6 internet ingress.

Explanation

Correct Answer

B:

Dual-stack needs an eligible IPv6 public frontend, protocol/rule support and the retained IPv4 path.

Incorrect Answers

A:

IPv4 DNS caching settings cannot create a valid IPv6 transport route.

C:

IPv6 loopback is local to the host and cannot serve public internet traffic.

D:

A private storage endpoint provides private PaaS connectivity, not dual-stack public ingress to this web service.

Question 638

A security review finds a VM public IP reachable on TCP 22 from the entire internet. Administrators require controlled remote administration. Which remediation is appropriate?

  1. Allow all ports on the public IP because SSH uses cryptography.
  2. Set the VM resource-group tag to Private.
  3. Publish a different DNS name but retain port 22 open to 0.0.0.0/0.
  4. Remove direct public SSH where feasible or restrict NSG sources and use Bastion/VPN for administration.

Explanation

Correct Answer

D:

Constrained management entry points and NSG source restrictions reduce exposure while retaining operator access.

Incorrect Answers

A:

SSH encryption does not justify unrestricted scanning/reachability of the management port.

B:

Resource tags do not implement packet-filtering rules.

C:

Changing DNS labels does not hide the still-open public endpoint.

Question 639

An Azure Standard public IP should have a service FQDN using the Azure regional cloudapp domain. Which property should the operator configure?

  1. Configure a unique Domain name label on the eligible public IP resource and verify the generated regional FQDN.
  2. Rename the VM managed disk to match the desired DNS hostname.
  3. Add a CNAME record inside an unrelated private DNS zone only.
  4. Enable private DNS auto-registration without assigning a public IP.

Explanation

Correct Answer

A:

Azure public IP domain name labels generate the public cloudapp FQDN when available and region-compatible.

Incorrect Answers

B:

Managed disk names are not internet DNS-label inputs.

C:

An unrelated private zone does not reserve an Azure regional public DNS label.

D:

Private VNet auto-registration is not a public-IP DNS name assignment.

Question 640

A TCP application has regional Standard public Azure Load Balancers in West Europe and East US. The client network permits only one unchanged IP address, and the company requires Azure to direct traffic to a healthy regional deployment across regions without DNS-based failover. Which Azure solution meets those constraints?

  1. Attach one regional-tier static public IP to the West Europe load balancer and assume it automatically spans East US.
  2. Deploy an Azure Global (cross-region) Standard Load Balancer with a Global-tier static public IP and place the regional public load balancers in its backend pool.
  3. Assign a new private IP address to each VM and rely on internet clients to reach both regional networks directly.
  4. Configure an Azure DNS A record with two rotating regional IP addresses and claim client DNS caches will always use exactly one immutable public IP.

Explanation

Correct Answer

B:

Azure Global Load Balancer is the cross-region tier of Azure Standard Load Balancer. Its Global-tier Standard public IP is a static anycast frontend advertised in participating regions, with regional public load balancers used as backends. It routes clients toward an eligible healthy regional deployment while retaining one advertised public IP address. This directly meets the TCP/Layer 4 and no-DNS-switchover requirements, subject to supported regions and service limitations.

Incorrect Answers

A:

Regional-tier public IP resources are associated with a single Azure region and do not automatically advertise an anycast frontend across multiple regions. A regional load balancer can handle local high availability, but if its region is unavailable it cannot by itself shift new connections to the service deployed in East US. The scenario requires a cross-region endpoint with one static IP.

C:

Private addresses are not internet-routable public frontend endpoints. Even if connectivity is provided through a private VPN or ExpressRoute network, separate VM private addresses do not provide the single public anycast IP requested by the client. This design does not implement automatic cross-region health-based routing through the Azure public load-balancing service.

D:

DNS-based routing can expose multiple address values or depend on TTLs and recursive resolver caching during failover. Clients cannot be guaranteed to observe one unchanging public IP when the authoritative record changes to a different regional endpoint. A Global Load Balancer uses one Global-tier static public frontend and selects its healthy regional public load balancers without requiring the client to switch DNS destinations.