Question 500
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. Which operational control would best prevent a recurrence of this exact failure mode?
- Preserve labeled counter baselines during incident and post-change reviews.
- Test microbursts with buffer and latency metrics rather than only averaged Mbps.
- Maintain a test matrix for application ports and source ranges during changes.
- Track sustained and burst traffic separately when changing service policers.
Explanation
Correct Answer
D:Track sustained and burst traffic separately when changing service policers. The control limits repetition of the described root condition: A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. During audits, confirm: Policer exceed counters and throughput tests align with the corrected contracted profile.
Incorrect Answers
A:Preserve labeled counter baselines during incident and post-change reviews. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
B:Test microbursts with buffer and latency metrics rather than only averaged Mbps. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
C:Maintain a test matrix for application ports and source ranges during changes. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Question 501
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A customer asks for smoother egress transmission under a contracted rate, but the solution immediately discards many short bursts due to aggressive policing. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect where traffic is metered and whether queue-based shaping could accommodate short bursts.
- Inspect supported policer exceed actions and PLP marking on out-of-profile packets.
- Correlate queue occupancy, peak burst size and scheduler buffer allocation.
- Identify the actual congested output interface and its per-class latency/drop metrics.
Explanation
Correct Answer
A:Inspect where traffic is metered and whether queue-based shaping could accommodate short bursts. This check examines the decisive condition for Shaping versus policing before any unrelated changes are made. The underlying mechanism is: Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter. The confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Incorrect Answers
B:Inspect supported policer exceed actions and PLP marking on out-of-profile packets. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Policer PLP remark. A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
C:Correlate queue occupancy, peak burst size and scheduler buffer allocation. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
D:Identify the actual congested output interface and its per-class latency/drop metrics. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Question 502
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A customer asks for smoother egress transmission under a contracted rate, but the solution immediately discards many short bursts due to aggressive policing. Which routing or service mechanism best explains the reported behavior?
- A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic.
- Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter.
- Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts.
- CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output.
Explanation
Correct Answer
B:Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops. The targeted correction is: Use supported egress shaping if buffering and added delay are acceptable, keeping a policer where required.
Incorrect Answers
A:A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Policer PLP remark. A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
C:Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
D:CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Question 503
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A customer asks for smoother egress transmission under a contracted rate, but the solution immediately discards many short bursts due to aggressive policing. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Excess packets are delivered when capacity exists but are preferentially dropped under congestion.
- Burst tests show bounded occupancy and materially fewer drops without violating other class allocations.
- Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
- Latency improves when the bottleneck's queue allocation protects the approved traffic class.
Explanation
Correct Answer
C:Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter.
Incorrect Answers
A:Excess packets are delivered when capacity exists but are preferentially dropped under congestion. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Policer PLP remark. A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
B:Burst tests show bounded occupancy and materially fewer drops without violating other class allocations. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
D:Latency improves when the bottleneck's queue allocation protects the approved traffic class. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Question 504
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A customer asks for smoother egress transmission under a contracted rate, but the solution immediately discards many short bursts due to aggressive policing. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use a supported higher-loss-priority remark action with an appropriate downstream RED profile.
- Tune the supported queue buffer allocation for measured burst characteristics.
- Apply coherent end-to-end queue treatment to the observed bottleneck interface.
- Use supported egress shaping if buffering and added delay are acceptable, keeping a policer where required.
Explanation
Correct Answer
D:Use supported egress shaping if buffering and added delay are acceptable, keeping a policer where required. The change addresses the root behavior described here: Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter. Verify success with: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Incorrect Answers
A:Use a supported higher-loss-priority remark action with an appropriate downstream RED profile. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Policer PLP remark. A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
B:Tune the supported queue buffer allocation for measured burst characteristics. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
C:Apply coherent end-to-end queue treatment to the observed bottleneck interface. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Question 505
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A customer asks for smoother egress transmission under a contracted rate, but the solution immediately discards many short bursts due to aggressive policing. Which operational control would best prevent a recurrence of this exact failure mode?
- Measure delay, buffer occupancy and loss together when replacing a policer with a shaper.
- Verify both excess traffic behavior under idle and congested conditions.
- Test microbursts with buffer and latency metrics rather than only averaged Mbps.
- Trace classification and scheduling at every congested hop during service acceptance.
Explanation
Correct Answer
A:Measure delay, buffer occupancy and loss together when replacing a policer with a shaper. The control limits repetition of the described root condition: Shaping delays packets in a queue to meet a rate whereas policing commonly drops or marks traffic exceeding its meter. During audits, confirm: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Incorrect Answers
B:Verify both excess traffic behavior under idle and congested conditions. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Policer PLP remark. A policer can, where supported, reclassify or mark packet loss priority instead of always discarding excess traffic. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
C:Test microbursts with buffer and latency metrics rather than only averaged Mbps. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
D:Trace classification and scheduling at every congested hop during service acceptance. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is Shaping versus policing and the confirming observation is: Short bursts are queued within designed limits and output conforms to the contracted rate without uncontrolled drops.
Question 506
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A shared access interface carries dozens of logical subscriber services; one flat scheduler cannot enforce both port capacity and per-customer contracted limits. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect scheduler-map assignment and minimum transmit-rate settings for the relevant queues.
- Inspect the hierarchy of subscriber, service and physical-port shapers on the egress path.
- Inspect effective interface-to-scheduler-map assignment rather than only global CoS objects.
- Separate output-queue drop counters from ingress policer exceed statistics and classify test flows.
Explanation
Correct Answer
B:Inspect the hierarchy of subscriber, service and physical-port shapers on the egress path. This check examines the decisive condition for Hierarchical subscriber QoS before any unrelated changes are made. The underlying mechanism is: Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates. The confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Incorrect Answers
A:Inspect scheduler-map assignment and minimum transmit-rate settings for the relevant queues. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Scheduler bandwidth guarantees. Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
C:Inspect effective interface-to-scheduler-map assignment rather than only global CoS objects. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Scheduler map unapplied. Creating CoS components does not affect a port unless their mappings are applied to the intended interface. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
D:Separate output-queue drop counters from ingress policer exceed statistics and classify test flows. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Question 507
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A shared access interface carries dozens of logical subscriber services; one flat scheduler cannot enforce both port capacity and per-customer contracted limits. Which routing or service mechanism best explains the reported behavior?
- Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share.
- Creating CoS components does not affect a port unless their mappings are applied to the intended interface.
- Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates.
- Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment.
Explanation
Correct Answer
C:Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget. The targeted correction is: Implement supported hierarchical schedulers with explicit parent and child rate budgets.
Incorrect Answers
A:Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Scheduler bandwidth guarantees. Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
B:Creating CoS components does not affect a port unless their mappings are applied to the intended interface. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Scheduler map unapplied. Creating CoS components does not affect a port unless their mappings are applied to the intended interface. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
D:Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Question 508
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A shared access interface carries dozens of logical subscriber services; one flat scheduler cannot enforce both port capacity and per-customer contracted limits. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Under controlled congestion, the priority class receives its configured service while aggregate capacity remains bounded.
- The operational interface displays the expected scheduler map and queue statistics match the design.
- The relevant drop counter increments only for the mechanism causing the observed service problem.
- Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Explanation
Correct Answer
D:Independent test subscribers respect their contracted limits while the parent port stays within its total service budget. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates.
Incorrect Answers
A:Under controlled congestion, the priority class receives its configured service while aggregate capacity remains bounded. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Scheduler bandwidth guarantees. Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
B:The operational interface displays the expected scheduler map and queue statistics match the design. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Scheduler map unapplied. Creating CoS components does not affect a port unless their mappings are applied to the intended interface. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
C:The relevant drop counter increments only for the mechanism causing the observed service problem. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Question 509
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A shared access interface carries dozens of logical subscriber services; one flat scheduler cannot enforce both port capacity and per-customer contracted limits. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Implement supported hierarchical schedulers with explicit parent and child rate budgets.
- Apply the intended scheduler and scheduler map to the egress interface.
- Apply the reviewed scheduler map to the exact egress interface.
- Use per-stage CoS monitoring before adjusting queue or policer parameters.
Explanation
Correct Answer
A:Implement supported hierarchical schedulers with explicit parent and child rate budgets. The change addresses the root behavior described here: Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates. Verify success with: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Incorrect Answers
B:Apply the intended scheduler and scheduler map to the egress interface. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Scheduler bandwidth guarantees. Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
C:Apply the reviewed scheduler map to the exact egress interface. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Scheduler map unapplied. Creating CoS components does not affect a port unless their mappings are applied to the intended interface. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
D:Use per-stage CoS monitoring before adjusting queue or policer parameters. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Question 510
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A shared access interface carries dozens of logical subscriber services; one flat scheduler cannot enforce both port capacity and per-customer contracted limits. Which operational control would best prevent a recurrence of this exact failure mode?
- Test congestion with simultaneous traffic classes after scheduler changes.
- Test aggregate oversubscription and isolated subscriber saturation scenarios.
- Check object references and interface application after configuration template changes.
- Preserve labeled counter baselines during incident and post-change reviews.
Explanation
Correct Answer
B:Test aggregate oversubscription and isolated subscriber saturation scenarios. The control limits repetition of the described root condition: Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates. During audits, confirm: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Incorrect Answers
A:Test congestion with simultaneous traffic classes after scheduler changes. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Scheduler bandwidth guarantees. Schedulers allocate output service characteristics; a forwarding class needs an applied scheduler map to receive its planned resource share. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
C:Check object references and interface application after configuration template changes. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Scheduler map unapplied. Creating CoS components does not affect a port unless their mappings are applied to the intended interface. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
D:Preserve labeled counter baselines during incident and post-change reviews. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is Hierarchical subscriber QoS and the confirming observation is: Independent test subscribers respect their contracted limits while the parent port stays within its total service budget.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests