101 · Question #711
An administrator sets up a web server for a new web application. The administrator cannot access the web server at is causing this issue?
The correct answer is A. The HTTP service only listens on localhost. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, Microsoft, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First
Question
An administrator sets up a web server for a new web application. The administrator cannot access the web server at is causing this issue?
Exhibit
Options
- AThe HTTP service only listens on localhost
- BThe users IP needs to be allowed to access
- CThe server needs to be restarted
- DThe HTTPS service Is not running
How the community answered
(24 responses)- A92% (22)
- C4% (1)
- D4% (1)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, Microsoft, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
11
Hiroshi T.Jun 26, 2026The correct answer is A. When a service binds only to 127.0.0.1 (localhost), it accepts connections exclusively from the local machine itself, so any request coming from an external address is refused at the network layer before authentication or firewall rules even enter the picture. This is a common misconfiguration in Apache (Listen 127.0.0.1:80), nginx (server listen directives scoped to 127.0.0.1), and similar daemons where the default or a prior admin intentionally restricted the bind address. The fix is to update the listen directive to 0.0.0.0 or the specific interface IP and reload the service. The other options are plausible distractors but the question stem says the service is running and reachable on the box itself, which rules out D and C, and B would manifest as a 403 or firewall drop rather than a connection refusal.
Orla P.Jun 26, 2026The answer is A, the HTTP service only listens on localhost. When a service binds to 127.0.0.1 instead of 0.0.0.0 or the server's actual network interface, it only accepts connections from the machine itself, so any request coming in from another device gets dropped before it even touches the application. This is a classic misconfiguration you will see in Linux web server setups where the default config or a custom bind directive points the service inward. Options B, C, and D are worth knowing as troubleshooting steps in other scenarios, but none of them explain why an external client cannot reach a freshly configured server that is already up and running, which is exactly the situation the question describes.
Bao N.Jun 27, 2026Solid breakdown, and worth adding that this trips people up on sims because the service shows as running and the port appears open locally via netstat or ss, so you have to actually check the bind address to catch it.
Brenda K.Jun 23, 2026Quick win, 30 seconds max. A is dead right, a service bound to 127.0.0.1 only accepts connections from the machine itself, so any outside request gets dropped before it even reaches your firewall rules. Flag B, C, and D as distractors and move on.
Luis F.Jun 26, 2026I thought D at first but localhost binding blocks ALL outside connections, so A.
Nina C.Jun 26, 2026A is right, HTTP bound to localhost means only that machine can reach it.
Fatima Z.Jun 29, 2026Right, and the slick mnemonic for this is LLOP, "Localhost Locks Out Public," so you never mix up 127.0.0.1 versus 0.0.0.0 on exam day.
Fatima Z.Jun 26, 2026Oh this one got me on my actual exam and I almost clicked B before my brain screamed "LOCALHOST LURES YOU IN," picture a server whispering sweet nothings only to itself at 127.0.0.1 and refusing every outside caller. The moment I remembered that HTTP can be configured to bind only to the loopback address, meaning nobody outside the machine can knock on that door no matter how many IPs you whitelist, I locked in A without a second glance.
Nina C.Jun 29, 2026Yes, and what helped it click for me is remembering that firewall rules and the binding address are two completely separate layers, so you could whitelist every IP on the planet in your firewall and it still would not matter if the service itself is only listening on 127.0.0.1.
Bao N.Jun 22, 2026Got burned by this same trap, localhost bind kills remote access every time.
Yusuf A.Jun 26, 2026I honestly went with B first because my senior always talks about firewall rules and IP whitelisting when someone cannot reach a new server, but then I thought about it more and realized if the HTTP service is only bound to 127.0.0.1 it never even accepts connections from the outside, so no amount of IP allowing would fix that. Option A makes the most sense here because the service itself is the bottleneck, not the access rules around it.