To implement Hierarchical-QoS (Multi-tiered scheduling), which of the following actions must be undertaken? (Choose three)

Question

Options

• AH-QoS capabilities must be enabled globally on the router
• BA scheduler-policy must be configured.
• CThe queues in the SAP-ingress and SAP-egress policies do not require additional configuration
• DThe network queue policy must be configured to make use of the scheduler-policy.
• EThe scheduler-policy must be referenced in the SAP-ingress and SAP-egress policies.
• FThe scheduler-policy must be applied on the service SAP.

• A
  3% (1)
• B
  74% (26)
• C
  9% (3)
• D
  14% (5)

Explanation

Implementing H-QoS on Nokia SR OS requires three sequential steps: create the scheduler-policy (B), bind it to the QoS policies by referencing it in the SAP-ingress/egress policies so queues can reference parent schedulers (E), and apply it directly on the SAP to instantiate the scheduling hierarchy (F). Without all three, the H-QoS hierarchy simply doesn't activate.

Why the distractors are wrong:

• A is wrong - there is no global H-QoS enable command on SR OS; it's configured per-service, not globally.
• C is wrong - queues do require additional configuration; each queue must be assigned a parent scheduler within the policy to participate in the hierarchy.
• D is wrong - network queue policies apply to network-facing (IES/VPRN trunk) interfaces, not SAPs; they are unrelated to SAP-level H-QoS.

Memory tip: Think "Build → Bind → Bolt on" - you Build the scheduler-policy, Bind it inside your SAP QoS policies, then Bolt it onto the SAP. If you miss any one of these three steps, the hierarchy won't work.

No community discussion yet for this question.