[AUDIO LOGO]
Congratulations on completing another skill.
Now it's time for a review in the form of a quiz.
So let's go ahead and jump in with our first question.
Which of the following are methods
to set the weight on the router?
So let's go down our list here, and see which ones are viable.
So answer number one is to set it globally
with a policy route.
There's actually two problems with this statement.
The first is that it says globally
and we don't set this globally, and it
says with a policy route, which possibly
is referring to PBR or policy based routing, maybe it's not.
But policy route is not really a thing.
So 1 would be an incorrect answer.
Number 2 is to set it directly on the neighbor configuration.
And we actually saw when we went through our demonstration,
that that is possible, so 2 definitely a correct answer.
Number 3 and 4, If we look at both of these,
they're very similar.
It's just one of them is on an outbound route map or policy
and the other one is inbound.
Well, remember that we are talking about the weight
attribute here, and the weight attribute is only local.
There would be no reason at all to set
this on an outbound route map because it
doesn't get sent to neighbors.
So the correct answer here would, of course, be 4.
We could set it in an inbound route map or route
policy, just not outbound.
Therefore, our two correct answers here are 2 and 4.
Next question.
Name any advantages to using soft reconfiguration
over route-refresh?
So once again, let's go down our list.
Number 1 says that it has an unaltered BGP table that
can be useful for troubleshooting,
and we did discuss that, that is true.
Having that unaltered copy of the BGP table from the neighbor
can be very, very helpful again, particularly
for that troubleshooting aspect.
Number 2, soft reconfiguration is the default behavior.
This is definitely not true.
We actually saw that on both iOS XE and iOS XR,
they will both default actually to doing route-refresh.
Number 3 soft reconfiguration is faster.
Well, it may be an incredibly small maybe even
unmeasurable advantage.
However, it is just doing a local replay out of RAM,
therefore, it would be faster than getting
the information resent over the network
again, even though it may not be measurable.
Number 4 soft reconfiguration uses less bandwidth overall.
Now keep in mind we're talking about bandwidth here.
Now either way, the prefixes need
to be sent from the neighbor.
But what this is referring to, is
when you actually do the soft reconfiguration or route
refresh.
This is going to take less bandwidth,
since it's a local replay.
And, of course, 5 is going for the whole less memory concept.
Well, it's not going to take less memory because we
are storing that local copy.
So 5 would also be incorrect.
It actually takes more RAM or memory,
so our correct answers here are 1, 3, and 4.
Final question, which of the following is correct?
So basically, if we analyze our answers, two of them
have to do with local preference and two of them
have to do with weight.
And both of them have to do with whether it's the entire AS
or only the local router.
So let's go down our list then, and figure out
which one is actually correct.
So number one is saying that the local preference
can affect the entire AS.
This is definitely true, because local preference
gets sent in our BGP updates.
So that would mean that 2 is not going to be true
since they're opposites.
Number 3, weight can affect the entire AS.
Again, weight does not get sent in BGP updates,
so it cannot be used to effect the entire AS.
Once again them being opposites, that
would make 4 correct for weight, it
can only affect the local router.
So that makes 1 and 4 our correct answers.
And that concludes this quiz.
If you find that you are missing any of the information needed
to answer these questions, I would
encourage you to go back and review the reference
sources on each question.
Otherwise, congratulations on completing Implementing
Outbound BGP Path Selection.
I hope this has been informative for you,
and I'd like to thank you for viewing.