Question 290
A Linux administrator evaluates: An application reports its service healthy inside the container while the host mapping sends requests to the wrong port. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: An application reports its service healthy inside the container while the host mapping sends requests to the wrong port. The recommended direct administrative response is: Inspect container network mode and published ports, expose only the required service to intended interfaces and confirm reachability. The relevant failure or security risk is: Publishing a service on all host interfaces can expose sensitive container ports even if the application was intended for loopback only. Validate success with: Network inspection and connection tests prove approved clients reach the container port and disallowed network sources cannot.
For the specific observation (An application reports its service healthy inside the container while the host mapping sends requests to the wrong port), the acceptance evidence is: Network inspection and connection tests prove approved clients reach the container port and disallowed network sources cannot. This verifies the action (Inspect container network mode and published ports, expose only the required service to intended interfaces and confirm reachability.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Publishing a service on all host interfaces can expose sensitive container ports even if the application was intended for loopback only.
Incorrect Answers
Systemd service start versus boot enablement (2.5) would demonstrate or implement: systemctl is-active and is-enabled give the intended independent states before and after a controlled restart. This choice can be useful for that problem, but it does not establish the Container port publishing and network isolation control being assessed here.
Systemd timers and journal-based execution checks (2.5) addresses another technical failure: An enabled timer without a valid service unit or a misread OnCalendar expression may never execute the task. The required paired action and test concerns Container port publishing and network isolation; a passing result for this alternative could leave that requirement unresolved.
Linux symbolic versus hard links (2.1) would demonstrate or implement: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed. The paired-answer requirement concerns Container port publishing and network isolation; this alternative does not provide the matching intervention and separate acceptance evidence.