Recover a reverse-proxied company portal

$ curl -I https://staff.northwind.test/ HTTP/2 502 $ curl -sS -o /dev/null -w '%{http_code}\n' http://192.0.2.35:9000/ 200 $ curl --max-time 5 http://192.0.2.35:9443/ curl: (28) Connection timed out $ sudo nginx -t syntax is ok test is successful $ sudo tail -n 2 /var/log/nginx/error.log 2026-08-13T09:14:32Z upstream timed out while connecting to upstream 192.0.2.35:9443 $ date -u +%FT%TZ 2026-08-13T09:18:07Z $ sudo ss -lntp | grep ':8182' <no output>

matching

Match each observation to the strongest conclusion it supports.

4 pts

APP-01:9000 returns HTTP 200 → Public HTTPS returns HTTP 502 → No process listens on RPX-01:8182 → nginx logs a timeout to APP-01:9443 →

Need a hint?

Start with the row and choice that have the most distinctive purpose, then use that pair to narrow the rest.

Show another hint

For each remaining pair, explain the relationship in one sentence before selecting it.

single choice

Which action is the best next recovery decision?

3 pts

Restore the intended application service on 9443, then activate and test the reviewed 8182 listener Repoint production nginx to 9000 because it returned 200 Create a second public DNS record for the same hostname Delete the existing tunnel and recreate every route

Need a hint?

Restate the exact outcome or failure the prompt asks about before comparing choices.

Show another hint

Eliminate choices that solve a nearby problem, change more than requested, or do not fit the evidence.

ordering

Order the checks from the innermost dependency to the public user path after recovery work.

4 pts

Drag the rows or use the arrow buttons to reorder.

1 From RPX-01, request the exact APP-01:9443 health endpoint
2 Confirm nginx listens on 127.0.0.1:8182
3 Request 127.0.0.1:8182 with the public Host header
4 Request the public HTTPS hostname and verify content, TLS, and status

Need a hint?

Identify the prerequisite that must happen first and the verification or documentation that belongs last.

Show another hint

For the middle steps, ask what must already be true before each action can safely happen.

multi select

Select the THREE choices that preserve the intended published-application design.

3 pts

Use a Published application hostname-to-service route Reuse the healthy tunnel with a dedicated loopback service URL Keep 8182 loopback-only so only the local connector reaches it Use a private Tunnel CIDR route as the public website mapping Add a duplicate manual DNS record even though the full-zone route created one Forward the router directly to APP-01:9443

Need a hint?

Evaluate each option independently against the scenario evidence instead of treating the list as one decision.

Show another hint

Choose only options that directly satisfy the prompt; being generally true is not enough.

Recover a reverse-proxied company portal

Preview · not independently reviewed

Inspect the evidence

Published path

Collected evidence

Complete the response

Match each observation to the strongest conclusion it supports.

Which action is the best next recovery decision?

Order the checks from the innermost dependency to the public user path after recovery work.

Select the THREE choices that preserve the intended published-application design.

Review your result

Attempt history

Question or answer look wrong?