Free Cisco SPRI 300-510 Actual Exam Questions - Question 1 Discussion
A network operator wants to expand the segment routing global block in upcoming
maintenance. The operator must ensure that the changes to the segment routing global block have
no adverse impacts on the prefix-sid associated with the loopback0 interface used within the OSPF
domain.
Which command can the operator use to enforce R2 to have a strict prefix-sid assignment to
loopback0?
It’s B, since it explicitly locks prefix-SID to loopback0 avoiding any global block conflicts.
Good point about B locking the SID explicitly under loopback0. Also, A’s use of "strict" at the interface level might not be supported in all IOS versions, so B seems safer here. B
I think A works too since it uses the "strict" keyword directly under the interface, which seems designed to lock the prefix-SID firmly. That might be more targeted than just assigning a value like in B. A
Maybe B makes sense here since it explicitly assigns a prefix-SID to loopback0, which should prevent any global block changes from affecting it. The other options don’t seem as strict about locking the SID.
B/D? Option B seems to be about strict prefix-SID assignment since it uses the explicit prefix-sid command under the interface, which should lock the SID to loopback0 regardless of changes to the global block. Option D is more about enabling segment routing globally but doesn’t specifically enforce strict prefix-sid assignment. So I’d rule out D here. The question focuses on ensuring no impact to the loopback0 prefix-SID, which points to B being more precise.
B/D? I’m thinking about the command that locks the prefix-SID to a specific value, so it doesn’t change even if the global block is expanded. Option B looks like it might enforce strict assignment by explicitly configuring the prefix-SID on the loopback interface. Option D could be related but seems less direct about strict enforcement. The question is about avoiding impact on the existing prefix-SID, so I’d choose the one that specifically ties the SID to the loopback interface without relying on global defaults.
C