McAfee-Secured Website

Exam Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Video Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 2

Question 10

After fixing the following network problem, what should the team verify: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic.

  1. A simulated restart restores service with the approved subscriber policy intact.
  2. Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention.
  3. Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.
  4. Test packets traverse each intended virtual function and no alternate path bypasses the security service.

Explanation

Correct Answer

D:

Test packets traverse each intended virtual function and no alternate path bypasses the security service. This confirms the approved response: Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure. It is relevant because: A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.

Incorrect Answers

A:

A simulated restart restores service with the approved subscriber policy intact. This would validate ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. The specific correction here is: Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.

B:

Peak-load tests meet packet loss and jitter objectives without unexpected host scheduling contention. This would validate ANOTHER scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The specific correction here is: Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.

C:

Synthetic timing and delay tests remain within the RAN interface limits at full traffic load. This would validate ANOTHER scenario: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. The specific correction here is: Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.

Question 11

A carrier root-cause review considers: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. What underlying mechanism explains this?

  1. A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.
  2. Container instances are replaceable runtime units and their writable layers are not reliable configuration stores.
  3. Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.
  4. Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.

Explanation

Correct Answer

A:

A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain. This explains the investigated issue: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. The approved corrective response is: Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.

Incorrect Answers

B:

Container instances are replaceable runtime units and their writable layers are not reliable configuration stores. That explains a DIFFERENT scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. The mechanism to prioritize for this question is: A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.

C:

Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. That explains a DIFFERENT scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The mechanism to prioritize for this question is: A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.

D:

Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths. That explains a DIFFERENT scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. The mechanism to prioritize for this question is: A VNF requires both compute execution and correctly bound virtual networking to participate in a forwarding chain.

Question 12

After addressing: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. Which recurring service assurance check is most useful?

  1. Run restart and rescheduling persistence drills before production upgrade windows.
  2. Include port binding and chain-path readback in migration automation.
  3. Audit hosted-app resource utilization and release compatibility on upgrades.
  4. Include platform and release detection before network software maintenance automation.

Explanation

Correct Answer

B:

Include port binding and chain-path readback in migration automation. This helps prevent recurrence of the issue: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. Acceptance evidence should be: Test packets traverse each intended virtual function and no alternate path bypasses the security service.

Incorrect Answers

A:

Run restart and rescheduling persistence drills before production upgrade windows. That is a sensible control for ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. It is less targeted to this issue than: Include port binding and chain-path readback in migration automation.

C:

Audit hosted-app resource utilization and release compatibility on upgrades. That is a sensible control for ANOTHER scenario: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. It is less targeted to this issue than: Include port binding and chain-path readback in migration automation.

D:

Include platform and release detection before network software maintenance automation. That is a sensible control for ANOTHER scenario: A technician deploys IOS XE package commands to an IOS XR route processor, then misinterprets the command rejection as a missing license. It is less targeted to this issue than: Include port binding and chain-path readback in migration automation.

Question 13

A provider backbone escalation identifies: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. What should the network team implement?

  1. Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy.
  2. Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing.
  3. Use the supported IOS XE software installation workflow for the platform and validate active package and boot state.
  4. Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence.

Explanation

Correct Answer

D:

Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence. This directly addresses the fictional service-provider network case: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. The technical mechanism is: MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries. Verify success by: Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified.

Incorrect Answers

A:

Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy. This would respond to a DIFFERENT fictional service-provider network issue: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. It does not directly address the current situation: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary.

B:

Apply stable, standards-consistent IPv6 flow-label generation for each flow where used by network load sharing. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. It does not directly address the current situation: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary.

C:

Use the supported IOS XE software installation workflow for the platform and validate active package and boot state. This would respond to a DIFFERENT fictional service-provider network issue: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It does not directly address the current situation: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary.

Question 14

A service-provider operations test targets: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. Which result is required?

  1. Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified.
  2. A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class.
  3. An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget.
  4. A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.

Explanation

Correct Answer

A:

Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified. This confirms the approved response: Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence. It is relevant because: MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

Incorrect Answers

B:

A dual-stream test shows only the approved interactive flows receiving reserved priority and bulk transfers using the contracted lower class. This would validate ANOTHER scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. The specific correction here is: Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence.

C:

An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget. This would validate ANOTHER scenario: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. The specific correction here is: Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence.

D:

A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site. This would validate ANOTHER scenario: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. The specific correction here is: Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence.

Question 15

A provider troubleshooting note states: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. Which mechanism is central?

  1. Maximum Allocation Model and Russian Dolls Model partition reservable bandwidth differently for traffic-engineering classes.
  2. MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.
  3. QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority.
  4. Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

Explanation

Correct Answer

B:

MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries. This explains the investigated issue: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. The approved corrective response is: Define the intended MPLS Pipe or Short Pipe QoS mapping and mark labels without unintentionally modifying customer IP precedence.

Incorrect Answers

A:

Maximum Allocation Model and Russian Dolls Model partition reservable bandwidth differently for traffic-engineering classes. That explains a DIFFERENT scenario: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. The mechanism to prioritize for this question is: MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

C:

QoS trust boundaries prevent arbitrary customer markings from obtaining unlimited provider scheduling priority. That explains a DIFFERENT scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. The mechanism to prioritize for this question is: MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

D:

Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. That explains a DIFFERENT scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The mechanism to prioritize for this question is: MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

Question 16

To prevent recurrence of this provider network issue: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. Which control should be retained?

  1. Capacity-test classifier, policer and scheduler state before service rollout.
  2. Include negative marking tests at each new customer UNI.
  3. Maintain a tested ingress-to-egress marking map for each QoS service class.
  4. Require peer and prefix authorization and monitor FlowSpec rule impacts.

Explanation

Correct Answer

C:

Maintain a tested ingress-to-egress marking map for each QoS service class. This helps prevent recurrence of the issue: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. Acceptance evidence should be: Captures before and after the provider domain show expected outer traffic-class values and preserved customer DSCP when specified.

Incorrect Answers

A:

Capacity-test classifier, policer and scheduler state before service rollout. That is a sensible control for ANOTHER scenario: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. It is less targeted to this issue than: Maintain a tested ingress-to-egress marking map for each QoS service class.

B:

Include negative marking tests at each new customer UNI. That is a sensible control for ANOTHER scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. It is less targeted to this issue than: Maintain a tested ingress-to-egress marking map for each QoS service class.

D:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Maintain a tested ingress-to-egress marking map for each QoS service class.

Question 17

At a global tier-one IP transit carrier, an engineering review finds: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. Which change most directly corrects the service problem?

  1. Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.
  2. Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.
  3. Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.
  4. Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.

Explanation

Correct Answer

A:

Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer. This directly addresses the fictional service-provider network case: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The technical mechanism is: GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic. Verify success by: The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Incorrect Answers

B:

Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action. This would respond to a DIFFERENT fictional service-provider network issue: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It does not directly address the current situation: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled.

C:

Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. This would respond to a DIFFERENT fictional service-provider network issue: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. It does not directly address the current situation: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled.

D:

Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary. This would respond to a DIFFERENT fictional service-provider network issue: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. It does not directly address the current situation: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled.

Question 18

For a global tier-one IP transit carrier, operators addressed: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. What is the strongest acceptance evidence?

  1. In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.
  2. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.
  3. Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.
  4. A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported.

Explanation

Correct Answer

B:

The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected. This confirms the approved response: Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer. It is relevant because: GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.

Incorrect Answers

A:

In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues. This would validate ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. The specific correction here is: Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.

C:

Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst. This would validate ANOTHER scenario: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. The specific correction here is: Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.

D:

A controlled process test restores the affected service while unrelated line-card forwarding remains stable where supported. This would validate ANOTHER scenario: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The specific correction here is: Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.

Question 19

Which network protocol or forwarding behavior explains the following issue: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled.

  1. LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.
  2. BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.
  3. GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.
  4. MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries.

Explanation

Correct Answer

C:

GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic. This explains the investigated issue: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The approved corrective response is: Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.

Incorrect Answers

A:

LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core. That explains a DIFFERENT scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The mechanism to prioritize for this question is: GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.

B:

BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity. That explains a DIFFERENT scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. The mechanism to prioritize for this question is: GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.

D:

MPLS QoS models determine how label traffic class and customer IP markings interact across provider boundaries. That explains a DIFFERENT scenario: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. The mechanism to prioritize for this question is: GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.

Question 20

A core network change board wants to avoid: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. Which ongoing safeguard fits best?

  1. Require peer and prefix authorization and monitor FlowSpec rule impacts.
  2. Audit LDP adjacencies and label allocation policy against topology inventory.
  3. Run restart and rescheduling persistence drills before production upgrade windows.
  4. Validate peer hop counts before applying TTL-security to multihop sessions.

Explanation

Correct Answer

D:

Validate peer hop counts before applying TTL-security to multihop sessions. This helps prevent recurrence of the issue: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. Acceptance evidence should be: The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Incorrect Answers

A:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Validate peer hop counts before applying TTL-security to multihop sessions.

B:

Audit LDP adjacencies and label allocation policy against topology inventory. That is a sensible control for ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. It is less targeted to this issue than: Validate peer hop counts before applying TTL-security to multihop sessions.

C:

Run restart and rescheduling persistence drills before production upgrade windows. That is a sensible control for ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. It is less targeted to this issue than: Validate peer hop counts before applying TTL-security to multihop sessions.