Pass Your Cisco 350-501 Exam Easy!

This defect belongs to SRv6 interworking gateway, where the affected outcome is to carry traffic between SRv6 and another provider service encapsulation domain. It is not the direct failure mode identified for the SR transit MTU planning design in this case: customer payload MTU is kept at the link maximum with no header allowance.

This defect belongs to MPLS-TE preemption priority, where the affected outcome is to allow higher-priority reservation requests to displace lower-priority capacity commitments. It is not the direct failure mode identified for the SR transit MTU planning design in this case: customer payload MTU is kept at the link maximum with no header allowance.

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 SR transit MTU planning design in this case: customer payload MTU is kept at the link maximum with no header allowance.

SRv6 micro SID compression instead addresses a different condition: reduce IPv6 segment-list header overhead on a compatible SRv6 domain. It would instead require you to use supported micro-segment locator and processing behavior, not the stated goal to carry traffic between SRv6 and another provider service encapsulation domain.

LDP address family transport instead addresses a different condition: carry the intended labeled IPv4 transport prefixes consistently across a provider core. It would instead require you to enable the supported address-family LDP capability on participating routers, not the stated goal to carry traffic between SRv6 and another provider service encapsulation domain.

PHP penultimate hop behavior instead addresses a different condition: avoid unnecessary label lookup at the final transport destination. It would instead require you to use the intended implicit-null or penultimate-hop-pop transport behavior, not the stated goal to carry traffic between SRv6 and another provider service encapsulation domain.

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 SRv6 interworking gateway operation: deploy an interworking PE or gateway with explicit service and forwarding mappings.

The proposed step is for LDP address family transport, whose purpose is to carry the intended labeled IPv4 transport prefixes consistently across a provider core. It would not perform the necessary SRv6 interworking gateway operation: deploy an interworking PE or gateway with explicit service and forwarding mappings.

The proposed step is for PHP penultimate hop behavior, whose purpose is to avoid unnecessary label lookup at the final transport destination. It would not perform the necessary SRv6 interworking gateway operation: deploy an interworking PE or gateway with explicit service and forwarding mappings.

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 SRv6 interworking gateway result: traffic crosses domains while customer route and isolation semantics remain correct.

The observation would verify LDP address family transport under the separate requirement to carry the intended labeled IPv4 transport prefixes consistently across a provider core. It does not demonstrate the needed SRv6 interworking gateway result: traffic crosses domains while customer route and isolation semantics remain correct.

The observation would verify PHP penultimate hop behavior under the separate requirement to avoid unnecessary label lookup at the final transport destination. It does not demonstrate the needed SRv6 interworking gateway result: traffic crosses domains while customer route and isolation semantics remain correct.

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 SRv6 interworking gateway design in this case: one domain's SID is forwarded unchanged into a device that cannot interpret it.

This defect belongs to LDP address family transport, where the affected outcome is to carry the intended labeled IPv4 transport prefixes consistently across a provider core. It is not the direct failure mode identified for the SRv6 interworking gateway design in this case: one domain's SID is forwarded unchanged into a device that cannot interpret it.

This defect belongs to PHP penultimate hop behavior, where the affected outcome is to avoid unnecessary label lookup at the final transport destination. It is not the direct failure mode identified for the SRv6 interworking gateway design in this case: one domain's SID is forwarded unchanged into a device that cannot interpret it.

node prefix SID forwarding instead addresses a different condition: steer a segment-routed packet to a particular node along its IGP shortest path. It would instead require you to use the node's advertised prefix SID in the appropriate segment list, not the stated goal to avoid calculating SR-TE paths from outdated connectivity or bandwidth state.

RSVP TE explicit path instead addresses a different condition: steer an MPLS TE tunnel over selected intermediate nodes rather than only IGP shortest path. It would instead require you to configure an RSVP-TE tunnel with a suitable explicit-route object, not the stated goal to avoid calculating SR-TE paths from outdated connectivity or bandwidth state.

LDP hello discovery timer resilience instead addresses a different condition: keep an LDP link adjacency stable through brief congestion without hiding real forwarding loss. It would instead require you to coordinate supported LDP hello interval and discovery holdtime settings on both core neighbors, not the stated goal to avoid calculating SR-TE paths from outdated connectivity or bandwidth state.

The proposed step is for node prefix SID forwarding, whose purpose is to steer a segment-routed packet to a particular node along its IGP shortest path. It would not perform the necessary PCE stale topology risk operation: synchronize PCE topology and performance feeds before delegated path calculation.

The proposed step is for RSVP TE explicit path, whose purpose is to steer an MPLS TE tunnel over selected intermediate nodes rather than only IGP shortest path. It would not perform the necessary PCE stale topology risk operation: synchronize PCE topology and performance feeds before delegated path calculation.

The proposed step is for LDP hello discovery timer resilience, whose purpose is to keep an LDP link adjacency stable through brief congestion without hiding real forwarding loss. It would not perform the necessary PCE stale topology risk operation: synchronize PCE topology and performance feeds before delegated path calculation.

The observation would verify node prefix SID forwarding under the separate requirement to steer a segment-routed packet to a particular node along its IGP shortest path. It does not demonstrate the needed PCE stale topology risk result: new paths reflect current links and constraints rather than a stale graph.

The observation would verify RSVP TE explicit path under the separate requirement to steer an MPLS TE tunnel over selected intermediate nodes rather than only IGP shortest path. It does not demonstrate the needed PCE stale topology risk result: new paths reflect current links and constraints rather than a stale graph.

The observation would verify LDP hello discovery timer resilience under the separate requirement to keep an LDP link adjacency stable through brief congestion without hiding real forwarding loss. It does not demonstrate the needed PCE stale topology risk result: new paths reflect current links and constraints rather than a stale graph.

This defect belongs to node prefix SID forwarding, where the affected outcome is to steer a segment-routed packet to a particular node along its IGP shortest path. It is not the direct failure mode identified for the PCE stale topology risk design in this case: PCE keeps selecting failed links because topology notification stopped.

This defect belongs to RSVP TE explicit path, where the affected outcome is to steer an MPLS TE tunnel over selected intermediate nodes rather than only IGP shortest path. It is not the direct failure mode identified for the PCE stale topology risk design in this case: PCE keeps selecting failed links because topology notification stopped.

This defect belongs to LDP hello discovery timer resilience, where the affected outcome is to keep an LDP link adjacency stable through brief congestion without hiding real forwarding loss. It is not the direct failure mode identified for the PCE stale topology risk design in this case: PCE keeps selecting failed links because topology notification stopped.

Flex Algorithm affinity exclusion instead addresses a different condition: exclude links carrying a forbidden administrative affinity from one SR shortest-path computation. It would instead require you to define the Flex Algorithm affinity constraint consistently on participants, not the stated goal to confirm that an SR policy actually follows an intended programmed forwarding path.

LDP directly connected hello discovery instead addresses a different condition: form LDP adjacency on a provider core link carrying labeled traffic. It would instead require you to enable compatible LDP link discovery on both facing interfaces, not the stated goal to confirm that an SR policy actually follows an intended programmed forwarding path.

SRLG diverse recovery instead addresses a different condition: avoid primary and backup TE paths sharing the same underlying fiber risk. It would instead require you to define and exclude common Shared Risk Link Groups in the recovery path computation, not the stated goal to confirm that an SR policy actually follows an intended programmed forwarding path.

The proposed step is for Flex Algorithm affinity exclusion, whose purpose is to exclude links carrying a forbidden administrative affinity from one SR shortest-path computation. It would not perform the necessary SR OAM path verification operation: run supported segment-routing OAM or policy traceroute verification.

The proposed step is for LDP directly connected hello discovery, whose purpose is to form LDP adjacency on a provider core link carrying labeled traffic. It would not perform the necessary SR OAM path verification operation: run supported segment-routing OAM or policy traceroute verification.

The proposed step is for SRLG diverse recovery, whose purpose is to avoid primary and backup TE paths sharing the same underlying fiber risk. It would not perform the necessary SR OAM path verification operation: run supported segment-routing OAM or policy traceroute verification.