-- Exhibit --
inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.23.10.0/24 *[Direct/0] 21:59:56
>via ge-0/0/6.0
172.23.10.100/32 *[Local/0] 22:00:10
Local via ge-0/0/6.0 -
172.23.12.0/24 *[Static/5] 00:01:36
>to 172.23.10.1 via ge-0/0/6.0
172.23.15.0/24 *[Static/5] 00:01:36
>to 172.23.10.1 via ge-0/0/6.0
-- Exhibit --
Users are unable to access resources in the 172.23.14.0/24 subnet.
Referring to the exhibit, which two actions would solve this problem? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D.BC
From the output of the exhibit, we see that there are four routes in the inet.0 routing table. The first route, 172.23.10.0/24, is a directly connected route, meaning that it is connected to the router's interface ge-0/0/6.0. The second route, 172.23.10.100/32, is a local route, which means that the router itself is the destination. The third and fourth routes are static routes, which specify that traffic destined for 172.23.12.0/24 and 172.23.15.0/24 should be forwarded to the next hop 172.23.10.1, which is also reachable via the ge-0/0/6.0 interface.
Now, we are given a problem that users are unable to access resources in the 172.23.14.0/24 subnet. This means that there is no route for this subnet in the routing table. To solve this problem, we need to add a route to the 172.23.14.0/24 subnet in the routing table.
Option A, "Configure a separate routing instance", is not required to solve the problem. A separate routing instance would create a new routing table and would not affect the existing routing table.
Option B, "Configure a default static route", is not the best solution because a default static route would only be used if there is no specific route in the routing table for the destination subnet. In this case, we know the destination subnet, 172.23.14.0/24, so it is better to add a specific static route for this subnet.
Option C, "Configure a static route to 172.23.14.0/24", is one of the correct solutions. We can add a static route for the 172.23.14.0/24 subnet with the next hop of 172.23.10.1 via the ge-0/0/6.0 interface. The command to add this route would be:
vbnetset routing-options static route 172.23.14.0/24 next-hop 172.23.10.1 interface ge-0/0/6.0 Option D, "Configure the existing routes to resolve the indirect next hop", is not a valid solution. The existing routes are already configured to forward traffic to the next hop 172.23.10.1, so there is no need to modify them.
In summary, the two correct actions to solve the problem of users unable to access resources in the 172.23.14.0/24 subnet are to configure a static route to this subnet and add the route to the routing table, and not to create a separate routing instance or a default static route.