A team recently deployed new hosts in a private network that fail to connect with a backend service running in a separate network segment. Network access lists are configured, and name resolution works. Which action would most likely restore connectivity?
Adjust the firewall to allow all traffic from the new hosts
Add a new entry so that the hosts know how to reach the backend network
Assign different addresses on the hosts that match the backend network
Change the DNS server so the hosts redirect requests
A missing or incorrect entry in the route table means traffic never reaches its intended destination. Adding a new path to forward messages from the hosts' network to the backend service segment resolves the issue. Changing DNS relates to name resolution, firewall settings manage allowed ports, and modifying IP addresses can break the existing design unless the route table is correct.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a route table and why is it important in networking?
Open an interactive chat with Bash
What are network access lists, and how do they differ from route tables?
Open an interactive chat with Bash
Why wouldn't changing IP addresses or a DNS server fix this issue?