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 77

Question 760

An Azure Standard Load Balancer distributes TCP traffic directly to VM backends. The application wants the original client source IP, but a developer proposes that Load Balancer generate an HTTP `X-Forwarded-For` header. What is accurate?

  1. Standard Load Balancer always terminates HTTP requests and creates X-Forwarded-For headers before forwarding.
  2. Use a storage account SAS to insert original source headers into TCP packets.
  3. The Layer 4 Load Balancer normally preserves client source IP in backend flows but does not operate as an HTTP reverse proxy that adds X-Forwarded-For.
  4. A health probe can be configured to rewrite each application HTTP request header.

Explanation

Correct Answer

C:

Layer 4 forwarding preserves client-address behavior appropriate to the flow; X-Forwarded-For requires an HTTP-aware proxy such as Application Gateway.

Incorrect Answers

A:

An Azure Load Balancer forwards transport flows at Layer 4, not by parsing every HTTP request as a reverse proxy.

B:

A SAS token is an Azure Storage authorization mechanism, not an HTTP request-header transformation feature.

D:

Health probes test backend health and do not add forwarding headers to live client traffic.

Question 761

All Load Balancer backend VMs show Running, yet an HTTP health probe configured for `/ready` port 8080 reports every instance unhealthy. What is the correct first diagnosis?

  1. Check whether each VM listener on TCP 8080 responds successfully on the `/ready` path and whether the probe can reach it.
  2. Conclude the app is healthy because the VM power state is Running.
  3. Increase the storage account capacity so a failed HTTP probe is ignored.
  4. Replace the load balancer with a public DNS record while keeping an unreachable probe.

Explanation

Correct Answer

A:

VM power state does not prove application health; the configured health endpoint, listening port, firewall path and HTTP response must satisfy the probe.

Incorrect Answers

B:

Running indicates VM resource state, not that the service responds correctly to its health check.

C:

Unrelated storage capacity does not repair a failed application HTTP health check.

D:

DNS records do not substitute for a working backend health probe in a Standard Load Balancer rule.

Question 762

One VM in a Standard Load Balancer backend pool reports an HTTP probe failure. On that VM, the configured `/health` endpoint returns HTTP 503 while the other instances return HTTP 200. Network security rules permit the probes. What should be fixed first?

  1. Choose global traffic-routing service rather than overconfigure a regional L4 balancer.
  2. Permit required AzureLoadBalancer probe traffic as appropriate.
  3. Fix its service endpoint/probe response before routing new traffic to it.
  4. Standardize compatible probe behavior or separate pools/rules.

Explanation

Correct Answer

C:

Investigate and repair the unhealthy application or its `/health` endpoint on the failing VM until the configured probe receives the required successful HTTP response. Azure Load Balancer excludes an unhealthy backend from new traffic; fixing the actual endpoint restores its eligibility.

Incorrect Answers

A:

A global DNS traffic-routing service would steer clients among external endpoints, not repair a particular VM whose local `/health` route returns HTTP 503. The current regional Load Balancer is working for other pool members.

B:

Network security rules already permit probe packets, which reach this VM and receive an HTTP 503. Adding an NSG allow rule cannot turn the application error response into a successful health-check reply.

D:

Separating pools is unnecessary when the same `/health` path exists across all instances and only one returns 503. The problem is the failing application endpoint, not incompatible health-probe path conventions.

Question 763

All backend VMs correctly serve HTTP 200 at the configured probe path, but a custom subnet NSG deny rule with higher priority blocks Azure Load Balancer probe traffic. What must be changed to allow healthy instances to receive new flows?

  1. Fix its service endpoint/probe response before routing new traffic to it.
  2. Permit required AzureLoadBalancer probe traffic as appropriate.
  3. Choose global traffic-routing service rather than overconfigure a regional L4 balancer.
  4. Choose a valid health endpoint/path and supported probe protocol.

Explanation

Correct Answer

B:

Create an appropriate higher-priority NSG allow rule for the AzureLoadBalancer service tag or documented 168.63.129.16 probe traffic on the health-probe port, then verify effective rules. The probe must reach the VM and receive HTTP 200 before the backend is considered healthy.

Incorrect Answers

A:

Restarting or rewriting the application endpoint would not address an NSG denial before the health probe reaches the VM. The application already responds successfully when tested locally.

C:

A global DNS routing service does not bypass subnet NSG security evaluation for the existing Azure Load Balancer backend VMs. It would neither authorize the blocked probe traffic nor restore backend health.

D:

The configured endpoint and protocol are already correct, so choosing a different health path does not remove the observed NSG deny. The network layer must allow the existing probe to reach the ready service.

Question 764

A public Standard Azure Load Balancer uses a TCP/443 rule to forward encrypted HTTPS traffic without terminating TLS. Its backend application returns HTTP 404 for GET `/` but serves an unauthenticated `/healthz` endpoint returning HTTP 200 on the configured HTTPS listener. The HTTPS health probe currently checks `/` and marks the backend unhealthy. What change fixes the health evaluation?

  1. Assign every VM an additional public IP to bypass the probe.
  2. Disable all backend NSG rules even though GET `/healthz` already reaches the application.
  3. Configure the HTTP/HTTPS health probe to use the validated `/healthz` path and correct listener port.
  4. Increase the application database storage quota, which makes root-path HTTP 404 count as healthy.

Explanation

Correct Answer

C:

Standard Load Balancer can use a separate HTTPS health probe even though its TCP load-balancing rule does not inspect URLs or terminate client TLS. Configure the probe path and backend listener port to request the verified `/healthz` endpoint; a returned HTTP 200 satisfies the documented HTTPS probe response requirement, whereas the current `/` returns 404.

Incorrect Answers

A:

A public VM IP would not change the incorrect HTTP path used by the load balancer health probe.

B:

The backend already answers the designated HTTPS /healthz path, so indiscriminately removing NSG rules does not correct the probe’s configured `/` path. Match the actual probe path, protocol and listener port instead of weakening network security.

D:

Database capacity does not change the fact that HTTP 404 at `/` is an unhealthy probe response.

Question 765

Load Balancer backend is empty after scaling a VM set. Which administrative action most directly meets the requirement?

  1. Verify peering/routes/NSG and frontend IP rather than replace the public DNS zone.
  2. Correct backend port mapping and confirm the VM process listener.
  3. Attach the intended VMSS/NIC backend pool correctly.
  4. Configure NAT Gateway or outbound rules according to supported network plan.

Explanation

Correct Answer

C:

A load balancer cannot distribute traffic to a scaled VMSS instance merely because a frontend rule exists: the intended scale set or NIC IP configurations must be associated with the backend pool. Repair the membership and confirm probe health and listener traffic on the newly added instances.

Incorrect Answers

A:

Peering and NSG checks affect packet paths; they do not fix an unhealthy backend listener or absent load-balancer rule.

B:

A port mismatch or stopped process can break traffic for a populated backend pool. Here the pool membership is empty following a VM scale set change, so correcting port mapping will still leave no backend destinations. Associate the scale set instances or eligible NIC IP configurations with the intended pool.

D:

NAT Gateway and outbound rules serve egress SNAT; they do not implement inbound listener health, load balancing or L7 routing.

Question 766

An internal Standard Load Balancer frontend is healthy according to backend health probes, and works from its own VNet. Clients in a peered VNet cannot reach the private frontend IP. Which investigation is the best first step?

  1. Inspect guest firewall/application binding and source/destination NSG rules.
  2. Use Application Gateway/appropriate L7 reverse proxy for HTTP routing and TLS termination.
  3. Verify peering/routes/NSG and frontend IP rather than replace the public DNS zone.
  4. Expose an appropriate health endpoint that answers supported unauthenticated probes without revealing sensitive application data.

Explanation

Correct Answer

C:

A Standard internal Load Balancer frontend is supported across properly configured VNet peering, including global peering; an inability to reach it from only the remote VNet therefore points to peering flags, effective routes, NSG/firewall rules or the frontend address. Check that network path first because the healthy local frontend and probes do not implicate a public DNS zone.

Incorrect Answers

A:

Guest listener/firewall and network-security rules can block a backend, but the stated frontend and probe already work from the local VNet. A failure isolated to clients in a peered VNet points first to cross-VNet reachability, peering flags, routing and client-to-frontend NSG rules, rather than changing the healthy backend process.

B:

Application Gateway performs HTTP(S) layer-seven routing and TLS termination; it isn't needed for plain TCP/UDP load-balancer port rules.

D:

A supported health endpoint is necessary when a configured health probe fails, but a failed private IP reachability test from a peered VNet doesn't establish an HTTP 401 or missing probe endpoint. First validate VNet peering, routes, NSG permissions, frontend IP and backend rule; only investigate health-probe responses when probe status confirms that cause.

Question 767

A Standard Azure Load Balancer forwards client TCP/443 connections to backend port 8443 without terminating TLS. The backend serves HTTPS GET /status with HTTP 200 on 8443, but rejects cleartext HTTP on that port. The custom health probe is configured as HTTP, port 8443, path /status; the NSG already permits the probe. Operations requires an application-level successful HTTPS response, not merely an open TCP socket. Which correction meets the requirement?

  1. Increase the HTTP probe failure threshold while keeping HTTP on the TLS-only port.
  2. Change the custom probe protocol to HTTPS on port 8443 with /status, keeping the TCP client load-balancing rule unchanged.
  3. Replace the probe with TCP on port 8443 and treat any reachable socket as proof that HTTPS GET /status returns HTTP 200.
  4. Convert the Standard Azure Load Balancer TCP rule into a Layer 7 HTTPS reverse proxy that terminates TLS and injects application credentials.

Explanation

Correct Answer

B:

Standard Load Balancer offers HTTPS probes, which negotiate TLS before issuing an HTTP GET against the specified probe path. Match HTTPS, backend listener port 8443 and /status so the probe can receive the expected HTTP 200. Its separate L4 client traffic rule can remain TCP and does not terminate TLS.

Incorrect Answers

A:

A larger failure threshold only delays marking unhealthy; it does not make a backend listening for TLS accept a cleartext HTTP GET. Probe protocol must match the actual backend listener.

C:

A TCP probe tests whether the three-way handshake succeeds, not whether an HTTPS request to /status completes successfully. It could mark a port healthy even while its HTTP application route is failing, contrary to the specified application-level health requirement.

D:

Azure Standard Load Balancer is a Layer 4 TCP/UDP load balancer, not an application-layer reverse proxy or TLS terminator. Changing the L4 rule cannot supply user tokens or fix a cleartext-versus-TLS probe transport mismatch.

Question 768

An Azure Standard public Load Balancer routes a long-lived TCP application to three healthy VM backends. Its application rule has a four-minute TCP idle timeout and TCP reset disabled. Clients legitimately pause for seven minutes between commands, after which the existing connection can no longer be used and neither endpoint is promptly notified of the stale flow. The application requires ten-minute idle gaps to remain usable and explicit notification when a connection eventually does time out. What change to this existing rule meets both needs?

  1. Change the health probe from TCP to HTTP but retain the four-minute idle timeout and disabled TCP reset.
  2. Increase the application load-balancing rule idle timeout to a supported value such as 15 minutes, and enable TCP reset on idle for that same TCP rule.
  3. Change the load-balancing rule to UDP without changing the application’s TCP socket code; UDP retains TCP sessions beyond four minutes.
  4. Recreate the VM network interface backend-pool association, leaving the existing four-minute timeout and disabled TCP reset untouched.

Explanation

Correct Answer

B:

Azure Standard Load Balancer supports a configurable idle timeout on TCP load-balancing rules, with a documented default of four minutes. Raising the rule’s timeout beyond the seven-minute pause, for example to 15 minutes, preserves eligible idle sessions for the required interval; enabling TCP reset provides bidirectional RST notification if a later idle timeout is reached.

Incorrect Answers

A:

Health probes determine which backend endpoints receive new traffic; changing probe protocol does not extend a connected TCP session’s idle lifetime or request RST notification to both endpoints. The configured four-minute idle limit remains.

C:

UDP does not preserve the semantics of an existing TCP connection and is not a drop-in fix for a TCP application. The requested stateful connection behavior is controlled by its TCP load-balancing rule idle timeout and TCP-reset settings.

D:

Pool membership changes determine where new load-balanced flows are directed, not the idle timeout of established TCP flows. Recreating NIC membership would introduce unnecessary disruption without changing the four-minute timeout or silent expiration behavior.

Question 769

A Standard Load Balancer shares one HTTP health probe configuration across its backend pool. Three VMs answer `/health`; a fourth healthy VM exposes its status only at `/healthz` and returns 404 on `/health`. All VM services run and NSGs allow probes. What is the sound remediation?

  1. Restart the fourth VM application even though it is serving requests and returning 200 at `/healthz`.
  2. Add an NSG allow rule even though all probes reach their configured endpoints.
  3. Change the subnet outbound NAT Gateway configuration for the healthy VM.
  4. Standardize a common healthy probe endpoint across all pool members, or separate workloads into pools/rules with compatible probes.

Explanation

Correct Answer

D:

Azure Load Balancer health probes use a configured protocol, port, and path for all backends associated with the rule. Expose the same path on each VM or partition different health endpoints into compatible pools and rules; then the probes receive expected HTTP 200 responses.

Incorrect Answers

A:

The fourth VM already serves its application and returns HTTP 200 on `/healthz`. A restart does not guarantee that `/health` becomes available and can introduce unnecessary downtime; the probe path mismatch must be fixed.

B:

The probes already reach `/health` and receive HTTP 404, so the blocking condition is not an NSG filter. An added allow rule cannot change an application HTTP response code or its route mapping.

C:

Outbound NAT controls connections initiated from the backend subnet. The failing health check is an inbound Load Balancer probe to a specific HTTP path. Changing NAT does not make `/health` return HTTP 200.

Question 770

A company wants to send clients in different countries to specified regional public web endpoints, using a geographic traffic-steering policy above the regional Azure Load Balancers. Which Azure service is suitable?

  1. Add a custom Layer 4 Load Balancer rule to inspect the client country and rewrite website DNS records.
  2. Use an Azure Traffic Manager profile with geographic routing and appropriately configured regional endpoints.
  3. Assign a service endpoint to each country to turn a regional balancer into a global geolocation-aware DNS service.
  4. Configure one internal Load Balancer private frontend and make it publicly geolocation-aware.

Explanation

Correct Answer

B:

Azure Traffic Manager supports DNS-based geographic routing methods to choose from configured regional endpoints for users.

Incorrect Answers

A:

Regional Layer 4 Load Balancer rules do not implement DNS-level country steering of separate geographic endpoints.

C:

Virtual network service endpoints provide selected service traffic paths, not global geographic web endpoint steering.

D:

An internal load balancer has a private frontend and does not become a public global DNS traffic router.