📝 Per hop behavior in DiffServ (12 MCQs)
📖 From Data Communication and Networks • 30. Quality of Service • 12 questions available
What is Per hop behavior in DiffServ?
Per Hop Behavior defines the forwarding treatment applied to a packet at each DiffServ-compliant router based on its DS codepoint, specifying queuing, scheduling, and dropping policies that collectively produce an aggregate end-to-end service class.
📝 All Per hop behavior in DiffServ MCQs
Q1. In an MPLS router, which statement best describes the immediate effect of the per‑hop behavior (PHB) when a labeled packet arrives?
📖 Explanation: The PHB is defined by the label value and dictates how the router should treat the packet at that hop, such as swapping the label, modifying the EXP bits, or setting QoS parameters. Therefore, the router’s forwarding decision is derived directly from the label, matching option B.
Q2. A packet arrives with a two‑label stack where the outer label maps to LSP A and the inner label maps to LSP B. According to MPLS per‑hop behavior, which label’s PHB is processed first?
📖 Explanation: MPLS processing follows a top‑down approach: the outermost label is examined first because it determines the immediate forwarding action, such as label swap or pop. After the outer label is handled, the packet’s new top label (formerly inner) is processed, making option C correct.
Q3. A PHB is configured to decrement the packet’s TTL and then classify the packet for QoS. If a packet arrives with TTL = 1, what will the router do after applying the PHB?
📖 Explanation: TTL is decremented as part of the PHB. When TTL becomes zero, the packet is considered expired and must be discarded to prevent routing loops. The subsequent QoS classification step is never reached, so the router drops the packet, which corresponds to option A.
Q4. In a network where some nodes only support Best‑Effort (BE) PHB, what happens to a packet marked with Expedited Forwarding (EF) when it reaches such a node?
📖 Explanation: If a node lacks support for EF, it cannot honor the high‑priority treatment. The standard behavior is to downgrade the packet to the highest PHB the node supports, which is BE. Consequently, the packet loses its EF priority, matching option D.
Q5. Which of the following best distinguishes MPLS per‑hop behavior from IPv4 DiffServ per‑hop treatment?
📖 Explanation: MPLS PHB decisions are based on the label attached to the packet, allowing fast label‑based forwarding. In contrast, DiffServ uses the DSCP field within the IP header to select queues. This fundamental difference is captured in option A, making it the correct answer.
Q6. If an MPLS label is associated with two different PHBs—one that swaps the label and another that only pushes a new label—what is the expected behavior?
📖 Explanation: A label can be bound to a single forwarding instruction set; having two conflicting PHBs on the same label is undefined. Implementations resolve this by prioritizing one PHB—typically the swap operation—while disregarding the other. Therefore the router applies only the swap PHB, aligning with option A.
Q7. Why can modifying the DSCP field after a label swap in a PHB lead to QoS inconsistency across an MPLS network?
📖 Explanation: When a PHB swaps a label, the packet’s forwarding path changes, but the DSCP field may remain unchanged. If the PHB also alters DSCP, downstream routers that rely on the original DSCP for queue selection may misinterpret the packet’s priority, causing a mismatch between intended and actual QoS treatment—hence option C.
Q8. How does static PHB assignment in LDP differ from dynamic PHB assignment in RSVP‑TE?
📖 Explanation: LDP typically distributes labels with a default PHB (often Best‑Effort) and does not negotiate QoS parameters. RSVP‑TE, on the other hand, can create explicit LSPs with specific PHBs tied to bandwidth reservations, allowing the PHB to be adapted per reservation. This distinction matches option C.
Q9. When designing a PHB for traffic engineering, how should the PHB interact with bandwidth reservation constraints?
📖 Explanation: The PHB must respect the amount of bandwidth that has been reserved for an LSP. If traffic exceeds the allocation, the PHB can shape or police the flow to keep it within limits, ensuring that the reservation is honored while still providing appropriate QoS. This aligns with option B.
Q10. Which combination of PHB mechanisms most effectively guarantees both bandwidth reservation and low latency for video streams across multiple MPLS domains?
📖 Explanation: RSVP‑TE can reserve exact bandwidth for a path, while an EF PHB provides low‑latency treatment by prioritizing packets in the forwarding plane. Combining these mechanisms in each MPLS domain ensures that video streams receive both guaranteed capacity and minimal queuing delay, making option A the most effective solution.
Q11. What is the relationship between the depth of a label stack and the processing overhead imposed by per‑hop behavior?
📖 Explanation: Each label in the stack requires the router to perform a lookup, apply the associated PHB, and possibly modify the stack. Consequently, as the number of labels increases, the cumulative processing time and resource usage increase proportionally, which is described by option C.
Q12. In MPLS terminology, what does the abbreviation PHB stand for?
📖 Explanation: PHB is the acronym for Per‑Hop Behavior, which defines the forwarding and treatment actions applied to a labeled packet at each MPLS hop. This definition directly matches option D.)