Pass Your Cisco 350-501 Exam Easy!

The proposed step is for SRv6 micro SID compression, whose purpose is to reduce IPv6 segment-list header overhead on a compatible SRv6 domain. It would not perform the necessary TI-LFA link repair operation: enable supported topology-independent LFA protection in the IGP.

The proposed step is for RSVP bandwidth reservation, whose purpose is to reserve a bounded amount of link bandwidth for an MPLS TE LSP. It would not perform the necessary TI-LFA link repair operation: enable supported topology-independent LFA protection in the IGP.

The proposed step is for LDP label binding verification, whose purpose is to check the label binding for a specific IGP destination before enabling a VPN. It would not perform the necessary TI-LFA link repair operation: enable supported topology-independent LFA protection in the IGP.

The observation would verify SRv6 micro SID compression under the separate requirement to reduce IPv6 segment-list header overhead on a compatible SRv6 domain. It does not demonstrate the needed TI-LFA link repair result: the local repair path forwards traffic immediately after the primary link fails.

The observation would verify RSVP bandwidth reservation under the separate requirement to reserve a bounded amount of link bandwidth for an MPLS TE LSP. It does not demonstrate the needed TI-LFA link repair result: the local repair path forwards traffic immediately after the primary link fails.

The observation would verify LDP label binding verification under the separate requirement to check the label binding for a specific IGP destination before enabling a VPN. It does not demonstrate the needed TI-LFA link repair result: the local repair path forwards traffic immediately after the primary link fails.

This defect belongs to SRv6 micro SID compression, where the affected outcome is to reduce IPv6 segment-list header overhead on a compatible SRv6 domain. It is not the direct failure mode identified for the TI-LFA link repair design in this case: the router waits for global SPF recomputation before repairing an eligible failure.

This defect belongs to RSVP bandwidth reservation, where the affected outcome is to reserve a bounded amount of link bandwidth for an MPLS TE LSP. It is not the direct failure mode identified for the TI-LFA link repair design in this case: the router waits for global SPF recomputation before repairing an eligible failure.

This defect belongs to LDP label binding verification, where the affected outcome is to check the label binding for a specific IGP destination before enabling a VPN. It is not the direct failure mode identified for the TI-LFA link repair design in this case: the router waits for global SPF recomputation before repairing an eligible failure.

TI-LFA link repair instead addresses a different condition: protect an SR transport link using a loop-free post-convergence backup. It would instead require you to enable supported topology-independent LFA protection in the IGP, not the stated goal to protect a traffic flow against failure of the adjacent intermediate node.

LDP session protection instead addresses a different condition: keep an LDP peer session through a brief loss of direct link connectivity. It would instead require you to enable supported LDP session protection and targeted-hello retention, not the stated goal to protect a traffic flow against failure of the adjacent intermediate node.

DS-TE class type allocation instead addresses a different condition: reserve traffic engineering resources separately for differentiated service classes. It would instead require you to apply the intended DS-TE bandwidth constraint model and class-type reservations, not the stated goal to protect a traffic flow against failure of the adjacent intermediate node.

The proposed step is for TI-LFA link repair, whose purpose is to protect an SR transport link using a loop-free post-convergence backup. It would not perform the necessary TI-LFA node protection operation: select a node-protecting TI-LFA backup rather than merely a link bypass.

The proposed step is for LDP session protection, whose purpose is to keep an LDP peer session through a brief loss of direct link connectivity. It would not perform the necessary TI-LFA node protection operation: select a node-protecting TI-LFA backup rather than merely a link bypass.

The proposed step is for DS-TE class type allocation, whose purpose is to reserve traffic engineering resources separately for differentiated service classes. It would not perform the necessary TI-LFA node protection operation: select a node-protecting TI-LFA backup rather than merely a link bypass.

The observation would verify TI-LFA link repair under the separate requirement to protect an SR transport link using a loop-free post-convergence backup. It does not demonstrate the needed TI-LFA node protection result: the repaired path avoids the failed neighbor node entirely.

The observation would verify LDP session protection under the separate requirement to keep an LDP peer session through a brief loss of direct link connectivity. It does not demonstrate the needed TI-LFA node protection result: the repaired path avoids the failed neighbor node entirely.

The observation would verify DS-TE class type allocation under the separate requirement to reserve traffic engineering resources separately for differentiated service classes. It does not demonstrate the needed TI-LFA node protection result: the repaired path avoids the failed neighbor node entirely.

This defect belongs to TI-LFA link repair, where the affected outcome is to protect an SR transport link using a loop-free post-convergence backup. It is not the direct failure mode identified for the TI-LFA node protection design in this case: a link-only bypass still traverses the failed node through another adjacency.

This defect belongs to LDP session protection, where the affected outcome is to keep an LDP peer session through a brief loss of direct link connectivity. It is not the direct failure mode identified for the TI-LFA node protection design in this case: a link-only bypass still traverses the failed node through another adjacency.

This defect belongs to DS-TE class type allocation, where the affected outcome is to reserve traffic engineering resources separately for differentiated service classes. It is not the direct failure mode identified for the TI-LFA node protection design in this case: a link-only bypass still traverses the failed node through another adjacency.

SRv6 End behavior instead addresses a different condition: process an SRv6 local End SID for transit forwarding to the next segment. It would instead require you to install the required local End function and forwarding information, not the stated goal to avoid a repair path sharing a common fiber-risk group with the failed path.

LDP router ID transport stability instead addresses a different condition: keep an LDP session bound to a stable routable label-switching router identity. It would instead require you to configure a reachable loopback router ID as the LDP transport endpoint, not the stated goal to avoid a repair path sharing a common fiber-risk group with the failed path.

RSVP fast reroute detour instead addresses a different condition: protect a traffic-engineered LSP locally against a planned link outage. It would instead require you to configure FRR backup protection for the affected RSVP-TE link or node, not the stated goal to avoid a repair path sharing a common fiber-risk group with the failed path.

The proposed step is for SRv6 End behavior, whose purpose is to process an SRv6 local End SID for transit forwarding to the next segment. It would not perform the necessary TI-LFA SRLG protection operation: enable supported SRLG-disjoint protection selection and valid risk-group topology data.

The proposed step is for LDP router ID transport stability, whose purpose is to keep an LDP session bound to a stable routable label-switching router identity. It would not perform the necessary TI-LFA SRLG protection operation: enable supported SRLG-disjoint protection selection and valid risk-group topology data.

The proposed step is for RSVP fast reroute detour, whose purpose is to protect a traffic-engineered LSP locally against a planned link outage. It would not perform the necessary TI-LFA SRLG protection operation: enable supported SRLG-disjoint protection selection and valid risk-group topology data.

The observation would verify SRv6 End behavior under the separate requirement to process an SRv6 local End SID for transit forwarding to the next segment. It does not demonstrate the needed TI-LFA SRLG protection result: the backup avoids the primary path's shared-risk link identifiers.

The observation would verify LDP router ID transport stability under the separate requirement to keep an LDP session bound to a stable routable label-switching router identity. It does not demonstrate the needed TI-LFA SRLG protection result: the backup avoids the primary path's shared-risk link identifiers.

The observation would verify RSVP fast reroute detour under the separate requirement to protect a traffic-engineered LSP locally against a planned link outage. It does not demonstrate the needed TI-LFA SRLG protection result: the backup avoids the primary path's shared-risk link identifiers.

This defect belongs to SRv6 End behavior, where the affected outcome is to process an SRv6 local End SID for transit forwarding to the next segment. It is not the direct failure mode identified for the TI-LFA SRLG protection design in this case: a nominally alternate link shares the same SRLG and fails in the same cut.

This defect belongs to LDP router ID transport stability, where the affected outcome is to keep an LDP session bound to a stable routable label-switching router identity. It is not the direct failure mode identified for the TI-LFA SRLG protection design in this case: a nominally alternate link shares the same SRLG and fails in the same cut.

This defect belongs to RSVP fast reroute detour, where the affected outcome is to protect a traffic-engineered LSP locally against a planned link outage. It is not the direct failure mode identified for the TI-LFA SRLG protection design in this case: a nominally alternate link shares the same SRLG and fails in the same cut.