i Think this is B and C
The question does not specify which PCE server is to be the primary.
so technically both D and E are correct depending on what you want to accomplish.
if you want the Primary PCE to remain the primary then add a PCE with a higher precedence.
If you want the Primary PCE to switch to the new PCE then set it at a lower precedence.
For this reason is why i think the answer is B and C.
Triggering PCE server precedence re-evaluation
A change in a PCE server’s precedence is not considered a PCE server failure.
So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC.
Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer.
By default, the TE reoptimisation timer is set to 3600 seconds.
You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers
or added new PCE servers. To do so, manually trigger TE reoptimisation.
Correct answer is B and C.
rm868, I agree with your post.
The meaning of question, it implies that PCE servers have already configured.
Answer D and E are incorrect based on this assumption.
Answer A is incorrect, it is unable to disable re-optimization timer (By default, the TE reoptimisation timer is set to 3600 seconds.).
Triggering PCE server precedence re-evaluation
A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC.
Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds.
You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode:
mpls traffic-eng reoptimize
why not B?
from the link in the question i quote:
"A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC."
so basically changing the precedence do not trigger a delegation, but adding a new PCE server does
In the above code snippet, 100 is a lower precedence than 255, which is the default precedence. Therefore, the device with IP address 192.0.2.2 becomes the primary PCE and the device with 192.0.2.1 becomes the standby PCE.
Triggering PCE server precedence re-evaluation
A change in a PCE server’s precedence is not considered a PCE server failure. So, the change in precedence does not trigger a redelegation timeout or a re-evaluation of LSP delegation to the PCE server at a PCC.
Re-evaluation of LSP delegation to PCE servers after CLI reconfiguration is controlled by the TE reoptimisation timer. By default, the TE reoptimisation timer is set to 3600 seconds.
You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode:
mpls traffic-eng reoptimize
I think C and D are the right answers. Here is why from the same link:
lower precedence => PCE is primary
The IP addreseses are compared incase of equal priority.
If the precedence for two PCEs is same, PCE with smaller IP address has a higher precedence.
You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode: mpls traffic-eng reoptimiz
its definitely E
If the precedence for two PCEs is same, PCE with smaller IP address has a higher precedence.
and its C.
You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode:
mpls traffic-eng reoptimize
all found on the same URL provided.
If a PCC is connected to multiple PCEs, the PCC selects a PCE
with the lowest precedence value. If there is a tie, a PCE with the highest IP address is chosen for computing path.
https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/segment-routing/72x/b-segment-routing-cg-ncs5500-72x.pdf
But in the question does not mention anything about the IPs, only regarding the precedence, no? and lower precedence --> primary PCE
A and C?. According to the link provided in the answer, a lower precedence PCE becomes the primary PCE and then "You can accelerate the re-evaluation of LSP delegation from a PCC to PCE servers after you have changed the precedence of PCE servers or added new PCE servers. To do so, manually trigger TE reoptimisation using the following command in privileged EXEC mode:mpls traffic-eng reoptimize"
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.350-501 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.
rm868
Highly Voted 3 years, 6 months agospyroskanel89
3 years, 1 month agomurmelika
Highly Voted 3 years, 11 months agorans3001
Most Recent 10 months agoMephystopheles
1 year, 10 months agoIcQ
1 year, 11 months ago1234512345
2 years, 1 month agothejag
2 years, 2 months agoDUsoo
2 years, 2 months agomohdema
2 years, 6 months agoelroy909
3 years, 5 months agoManuJi
7 months, 2 weeks agorokk_cm
3 years, 11 months agobeenardino
3 years, 11 months agomurmelika
3 years, 11 months agobeenardino
3 years, 11 months agorokk_cm
3 years, 11 months agobeenardino
3 years, 11 months agomurmelika
3 years, 11 months ago