A multinational enterprise with multiple branch offices notices that traffic from several departments fails to reach the main data center. Firewall logs show no blocks, and VLAN configurations are confirmed. Network administrators discover that entries for the affected subnets do not appear in the aggregator’s routing table. What is the most likely reason for these frequent disruptions?
A missing or misconfigured route statement in the network devices
Conflicting translations for sites with similar public address ranges
A trunk interface sending traffic with tagging issues at the local switch
An inbound rule on a perimeter device that blocks department traffic
A missing or misconfigured route statement leads to unreachable subnets or dropped packets, which aligns with the scenario of missing entries in the routing table. A firewall rule tends to block traffic outright rather than creating intermittent disruptions. Overlapping translations cause address conflicts rather than partial traffic losses. Trunk misconfigurations cause tagging issues at the local switch, not missing routing entries.
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.
How do routing tables work in a network?
Open an interactive chat with Bash
What can cause route statements to be misconfigured or missing?
Open an interactive chat with Bash
What are VLANs and how do they interact with routing?