Cisco® 642-887 Exam Practice Questions (P. 2)
- Full Access (183 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #6
When configuring LLQ (strict priority queue) on a traffic class using the Cisco IOS XR priority command on a Cisco ASR9K router, which additional QoS command is required for this traffic class?
- Ashape
- Bpolice
- Crandom-detect
- Dbandwidth
Correct Answer:
B
The Low Latency Queueing feature brings strict priority queueing to Class-Based Weighted Fair Queueing (CBWFQ).
B
The Low Latency Queueing feature brings strict priority queueing to Class-Based Weighted Fair Queueing (CBWFQ).
send
light_mode
delete
Question #7
On the Cisco ASR9K router, when using the bandwidth command to specify the minimum guaranteed bandwidth to be allocated for a specific class of traffic, what will be used as the queuing algorithm?
- Acustom queuing
- BCBWFQ
- CWFQ
- DFIFO
- Epriority queuing
Correct Answer:
B
Class based weighted fair queuing (CB-WFQ) was initially released without the support of a priority queuing system, thus it could not guarantee the delay and jitter
(delay variation) requirements of real-time, interactive voice and video conversations. Since for CBWFQ, the weight for a packet belonging to a specific class is derived from the bandwidth assigned to the class, which in turn determines the order in which packets are sent.
All packets are serviced fairly based on weight and no class of packets may be granted strict priority. This scheme poses problems for voice traffic that is largely intolerant of delay, especially variation in delay
B
Class based weighted fair queuing (CB-WFQ) was initially released without the support of a priority queuing system, thus it could not guarantee the delay and jitter
(delay variation) requirements of real-time, interactive voice and video conversations. Since for CBWFQ, the weight for a packet belonging to a specific class is derived from the bandwidth assigned to the class, which in turn determines the order in which packets are sent.
All packets are serviced fairly based on weight and no class of packets may be granted strict priority. This scheme poses problems for voice traffic that is largely intolerant of delay, especially variation in delay
send
light_mode
delete
Question #8
When implementing MPLS DS-TE on Cisco IOS XR routers, all aggregate Cisco MPLS TE traffic is mapped to which class type by default?
- Aclass-type 0 (bandwidth global pool)
- Bclass-type 1 (bandwidth subpool)
- Cclass-type 2 (bandwidth priority)
- Dclass type class-default (bandwidth best-effort)
Correct Answer:
A
Differentiated Services Traffic Engineering
MPLS Differentiated Services (Diff-Serv) Aware Traffic Engineering (DS-TE) is an extension of the regular MPLS-TE feature. Regular traffic engineering does not provide bandwidth guarantees to different traffic classes. A single bandwidth constraint is used in regular TE that is shared by all traffic. To support various classes of service (CoS), users can configure multiple bandwidth constraints. These bandwidth constraints can be treated differently based on the requirement for the traffic class using that constraint.
MPLS diff-serv traffic engineering provides the ability to configure multiple bandwidth constraints on an MPLSenabled interface. Available bandwidths from all configured bandwidth constraints are advertised using IGP.
TE tunnel is configured with bandwidth value and class-type requirements. Path calculation and admission control take the bandwidth and class-type into consideration. RSVP is used to signal the TE tunnel with bandwidth and class-type requirements.
Diff-Serv TE can be deployed with either Russian Doll Model (RDM) or Maximum Allocation Model (MAM) for bandwidth calculations.
TE Class Mapping -
Each of the eight available bandwidth values advertised in the IGP corresponds to a TE Class. Because the IGP advertises only eight bandwidth values, there can be a maximum of only eight TE classes supported in an IETF DS-TE network.
TE class mapping must be exactly the same on all routers in a DS-TE domain. It is the responsibility of the operator configure these settings properly as there is no way to automatically check or enforce consistency.
The operator must configure TE tunnel class types and priority levels to form a valid TE class. When the TE class map configuration is changed, tunnels already up are brought down. Tunnels in the down state, can be set up if a valid TE class map is found.
Table 4 TE Classes and Priority -

The default mapping includes four classes types.
A
Differentiated Services Traffic Engineering
MPLS Differentiated Services (Diff-Serv) Aware Traffic Engineering (DS-TE) is an extension of the regular MPLS-TE feature. Regular traffic engineering does not provide bandwidth guarantees to different traffic classes. A single bandwidth constraint is used in regular TE that is shared by all traffic. To support various classes of service (CoS), users can configure multiple bandwidth constraints. These bandwidth constraints can be treated differently based on the requirement for the traffic class using that constraint.
MPLS diff-serv traffic engineering provides the ability to configure multiple bandwidth constraints on an MPLSenabled interface. Available bandwidths from all configured bandwidth constraints are advertised using IGP.
TE tunnel is configured with bandwidth value and class-type requirements. Path calculation and admission control take the bandwidth and class-type into consideration. RSVP is used to signal the TE tunnel with bandwidth and class-type requirements.
Diff-Serv TE can be deployed with either Russian Doll Model (RDM) or Maximum Allocation Model (MAM) for bandwidth calculations.
TE Class Mapping -
Each of the eight available bandwidth values advertised in the IGP corresponds to a TE Class. Because the IGP advertises only eight bandwidth values, there can be a maximum of only eight TE classes supported in an IETF DS-TE network.
TE class mapping must be exactly the same on all routers in a DS-TE domain. It is the responsibility of the operator configure these settings properly as there is no way to automatically check or enforce consistency.
The operator must configure TE tunnel class types and priority levels to form a valid TE class. When the TE class map configuration is changed, tunnels already up are brought down. Tunnels in the down state, can be set up if a valid TE class map is found.
Table 4 TE Classes and Priority -

The default mapping includes four classes types.
send
light_mode
delete
Question #9
On the Cisco IOS XR, which MQC configuration is different than on the Cisco IOS and IOS XE?
- AOn the Cisco IOS XR, WRED can only be applied in the output direction.
- BOn the Cisco IOS XR, marking can only be applied in the input direction.
- COn the Cisco IOS XR, LLQ can be applied in the input or output direction.
- DOn the Cisco IOS XR, LLQ can use up to four priority queues: level 1, level 2, level 3, and level 4.
Correct Answer:
C
C
send
light_mode
delete
Question #10
On Cisco routers, how is hierarchical QoS implemented?
- AWithin the parent policy, reference another child policy using the policy-map command.
- BWithin the child policy, reference another parent policy using the policy-map command.
- CUse the policy-map command within a service-policy to implement nested policy-maps.
- DWithin the parent policy-map, reference another child policy-map using the service-policy command.
Correct Answer:
D
D
send
light_mode
delete
All Pages