ITForMe Beta Sign in
NET+ N10-009 V9 Network troubleshooting Supplemental practice Fictional web platform recovery · 1 of 4 Runs in your browser · no setup Original practice · Review pending

Recover a reverse-proxied company portal

Trace a public 502, repair the lost application-subnet route, and restore the reviewed tunnel-to-proxy path.

Estimated18 min
DifficultyAdvanced
Points14
Scenario brief

Northwind Orchard's public staff portal failed after a power outage rebooted RPX-01. A managed edge tunnel runs beside nginx on RPX-01. Before the outage, the application-subnet route had been added only to the running system and nginx had been started by hand. The change window permits service recovery and evidence gathering, but not an unreviewed architecture change.

Content record

Original practice · Review pending

Related product practice for CompTIA N10-009 learners · Does not count as exam-objective readiness · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.

Community review →
5.1Explain the troubleshooting methodology. 5.3Given a scenario, troubleshoot common issues with network services.
Show review record and official sources

Method: Mapped to N10-009 troubleshooting objectives 5.1 and 5.3; status-code interpretation, exact-upstream testing, persistent route recovery, and tunnel-route choices were rechecked against current Cloudflare and NetworkManager documentation. Scenario evidence and answer keys were revised in an AI editorial pass on 2026-10-06; that revision has had no independent review.

Current-profile check: 2026-08-12 · Next review due 2027-02-08

01

Inspect the evidence

Use only the information provided to complete the tasks.

Published path

list
  • ›staff.northwind.test → managed edge → existing tunnel → http://127.0.0.1:8182
  • ›nginx 127.0.0.1:8182 → APP-01 192.0.2.35:9443
  • ›Reviewed design: RPX-01 reaches the APP-01 subnet 192.0.2.32/28 through the internal router 198.51.100.254 on rpx-lan
  • ›The default gateway 198.51.100.1 is the Internet router; it has no route to 192.0.2.32/28

Collected evidence

code
$ curl -I https://staff.northwind.test/
HTTP/2 502
$ ping -c 2 198.51.100.254
2 packets transmitted, 2 received, 0% packet loss
$ curl --max-time 5 http://192.0.2.35:9443/
curl: (28) Connection timed out
$ sudo nginx -t
syntax is ok
test is successful
$ systemctl is-enabled nginx
disabled
$ systemctl is-active nginx
inactive
$ sudo ss -lntp | grep ':8182'
<no output>

Edge tunnel route types (provider runbook)

list
  • ›Published application route: maps one public hostname to one local service URL. With the DNS zone hosted by the same provider, creating the route also creates the hostname's DNS record.
  • ›Private network (CIDR) route: carries traffic from enrolled private clients to an internal IP range. It does not publish a public website.
  • ›One tunnel can carry several published application routes, each with its own local service URL.

RPX-01 route state after the outage

code
$ ip -br address
lo UNKNOWN 127.0.0.1/8
rpx-lan UP 198.51.100.24/24
$ ip route
default via 198.51.100.1 dev rpx-lan
$ nmcli connection show rpx-lan
GENERAL.STATE: activated
ipv4.routes: --
02

Complete the response

Partial credit is available for matching, ordering, and multi-select tasks.

Changes will save automatically.
01
matching

Match each observation to the strongest conclusion it supports.

4 pts
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.

02
single choice

Which action is the best next recovery decision?

3 pts
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.

03
linux cli

Use the isolated RPX-01 shell to diagnose the path, restore the reviewed APP-01 subnet route through 198.51.100.254 in both the active and persistent network profile, restore nginx now and after reboot, then verify the exact backend, local proxy, and public URLs.

4 pts
rpx-01systemd service recovery
Browser shell
This is an isolated Linux networking shell. Commands change only the published scenario state.
Need a hint?

Inspect the current files, permissions, logs, or service state before changing anything; use help to review the bounded command set.

Show another hint

Make the smallest state change supported by the evidence, then rerun the relevant checks to verify the result.

04
multi select

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

3 pts
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.

Ready to check your work?Unanswered tasks and matches earn no points. A partial submission is scored and saved in your history.
Persistent progress

Attempt history

Every submission is retained. Starting another attempt never replaces or unlocks the previous one.

No attempts yet

Your first submitted score and detailed answer review will appear here.

Community quality control

Question or answer look wrong?

Proposals and votes help staff prioritize review. They never change the scoring key automatically.

Full review queue →
No community corrections yet

Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.

Propose a correction