mediumMultiple ChoiceObjective-mapped

XK0-006 Practice Question: Refer to the exhibit

Exhibit

# /etc/nginx/nginx.conf (partial)
http {
    upstream backend {
        server backend1.example.com weight=5;
        server backend2.example.com weight=3;
        server backend3.example.com weight=2;
    }
    server {
        listen 80;
        location / {
            proxy_pass http://backend;
            proxy_next_upstream error timeout invalid_header http_500 http_502;
        }
    }
}

Refer to the exhibit. A system administrator notices that backend1.example.com is receiving significantly more traffic than the other two servers. What is the most likely reason?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Weighted load balancing distributes traffic proportionally; backend1 has the highest weight.

The upstream block uses weighted round-robin with weights 5, 3, and 2. The total weight is 10, so backend1 receives 5/10 = 50% of requests, backend2 receives 30%, and backend3 receives 20%. This distribution matches the observed pattern. Option A is incorrect because session persistence is not configured. Option C is incorrect because there is no health check mechanism shown. Option D is irrelevant as the proxy_next_upstream directive only affects retries on failure.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Session persistence (sticky sessions) is enabled, routing returning users to the same server.
Why it's wrong here
No sticky session configuration is present.
✓
Weighted load balancing distributes traffic proportionally; backend1 has the highest weight.
Why this is correct
With weight=5, backend1 gets the largest share of traffic.
✗
backend1 is the only server that passes health checks.
Why it's wrong here
No health check configuration is shown; all servers are assumed healthy.
✗
The proxy_next_upstream directive causes requests to be retried on backend1 first.
Why it's wrong here
proxy_next_upstream retries on failure, not initial distribution.

Go deeper

XK0-006 Practice Question: Refer to the exhibit

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question