i think this is B and C The question does not say which PCE server should be the primary. so technically both D and E are right depending on what you are trying to do. if you want the Primary PCE to stay primary then add a PCE with higher precedence. If you want the Primary PCE to change 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 treated as 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 speed up 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.

sorry, i meant C and D

Yes, but lower precedence means it has a better shot at being the primary, so definitely not E

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

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 speed up 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 speed up 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.

you are right sir!

yes you are right! ( I also said this about Murmelika earlier)

The answer is kind of in the question, since it talks about delegating the current primary, so C and D seem like the best fit.

A and C?. According to the link provided in the answer, a lower precedence PCE becomes the primary PCE and then "You can speed up 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"

Correct answer is B and C. rm868, I agree with your post. The meaning of question, it implies that PCE servers have already been 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.).

Selected Answer: CD 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 treated as 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 speed up 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

Selected Answer: BC Answers are B/C

B and C

C and D are better to me than C and B

Selected Answer: CD 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 does not trigger a delegation, but adding a new PCE server does

Selected Answer: CD LSP Delegations as per link: -Enter "#mpls traffic-eng reoptimize", and add new PCE server (lower precedence)

Selected Answer: BC Triggering PCE server precedence re-evaluation A change in a PCE server’s precedence is not treated as 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 speed up 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

this! It's asking about "delegation", i.e., making a new primary. Thus the new server has to come in with lower-precedence.