Its B
1) Try NH 1.1.1.1 (Seq 10)
2) Try NH 2.2.2.2 (Seq 20)
3) Try default NH 3.3.3.3 (Seq 30)
4) Match interface null, which means drop the packet. (Seq 40)
C is not correct, as interface null action will drop packets before the fallback to routing table can be leveraged.
"interface null: equivalent to the policy drop policing action. Any packets matching the class criteria for that policy entry will be dropped and not routed any further."
https://www.arubanetworks.com/techdocs/AOS-CX/10.05/HTML/5200-7300/index.html#GUID-DC7E5E47-8F31-4DE4-B257-1A68665B2AF4.html
C is correct... If 1.1.1.1 is not reachable then next hop uses 2.2.2.2 if both of these are unreachable then normal routing table is used..and only if no route is available in routing table then default next-hop will kick-in
"If the highest priority list entry next-hop router or tunnel interface is reachable - that list entry is chosen, the search is stopped, and the traffic is forwarded to the next-hop router or interface for the entry. If the highest priority list entry next-hop router or tunnel interface is not reachable, the next highest priority list entry reachability is determined and used if reachable, otherwise the process continues down the list. If none of the routers in the list are reachable, the packet may be dropped (through the null interface entry if configured) or forwarded according to a system route table entry."
If the null interface wasnt there it woulduse system routing, but since it is: drop
B: is the closest: If none of the routers in the list are reachable, the packet may be dropped (through the null interface entry if configured) or forwarded according to a system route table entry.
Page 905 Study Guide:
The figure shows that 4 packets have arrived at some interface, sitting in a queue, waiting for service. If the ingress buffer used a single queue, Head Of Line (HOL) blocking could delay traffic. This occurs when the first packet in the queue (at the “head of the line”) is destined out a congested port, it delays all packets behind it, even though those that are destined to noncongested ports. | AOS- CX switches use an intra- switch queuing method called Virtual output Queuing ( VoQ ). VOQ prevents this problem by providing deep ingress buffers with separate queues for each egress port.
[Aruba Networks]
B: If none of the routers in the list are reachable, the packet may be dropped (through the null interface entry if configured) or forwarded according to a system route table entry.
Answer is B. A PBR action list is processed from the top down like an ACL. After the three nexthop entries, there's an interface null entry. This will drop all traffic that matches on the pbr-action-list.
From manual: If none of the routers in the list are reachable, the packet may be dropped (through the null interface entry if configured) or forwarded according to a system route table entry.
Answer is B
interface null means that if all three are unreachable packets are dropped, only B works for me:
The active entry is the one with the lowest sequence number – the one entered first, by default. (1.1.1.1) This next hop is used exclusively unless that address becomes unavailable. Within 5 seconds, the router uses the next entry – 2.2.2.2. If both of those are down, then the router uses the default- nexthop 9.9.9.9. If all three are down, the interface null action ensures packets are merely thrown away. If you omit the interface null command, then the router falls back to using destination- based route table entries.
I think its C. If nexthop 1.1.1.1 is unreachable it will try nexthop 2.2.2.2.. If that one is also unreachable it will go toward the default-nexthop policy. Book explains default-nexthop as: Used if no specific route exists in routing table. So i believe it will first look at the routing table to foward the traffic, if there is no route there.. It will try 9.9.9.9, if that one is also unreachable he will drop the traffic because of interface null.
I must correct myself. I think it's C. More than one next hop can be assigned with an ACL and they work by priority (based on the sequence number: lower sequence number -> higher priority). So next-hop 2.2.2.2 will be used if 1.1.1.1 is not reachable.
If both are unreachable, then the packet will be routed looking at the default routing table, if no specific entry will be found, then the pacjet will be routed to the default next hop defined in the ACL.
I think it's b. PBR action list works like an ACL. Every entry is checked one by one and the first match is used. If the next hops are unavailable they don't match and it comes to interface null which iss the equivalent to dropping traffic.
This section is not available anymore. Please use the main Exam Page.HPE6-A73 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
asciithrowaway
Highly Voted 3 years, 6 months agoLinares1234
3 years, 6 months agojordib4
3 years, 3 months agoMrvn
Highly Voted 3 years, 9 months ago506e61e
Most Recent 8 months, 3 weeks agoA10busted
1 year, 7 months agoSeidorBruno
1 year, 9 months agoslotblocker
1 year, 10 months agoRedrum702
1 year, 11 months agotheklee
2 years, 4 months agoAlialo
2 years, 5 months agokarlkurt
2 years, 6 months agoRockford
2 years, 6 months agoNetExpert
2 years, 7 months agoHuanChing
2 years, 10 months agororzabal
2 years, 11 months agoLuc
3 years, 2 months agoLuke80
3 years, 2 months agoclupato2
3 years, 8 months agoclupato2
3 years, 8 months ago[Removed]
3 years, 9 months ago