Juniper Updated JN0-664 Exam Questions and Answers by angelo

Class of Service (CoS) in networking is used to manage traffic by classifying, scheduling, and sometimes modifying packets to ensure network performance and Quality of Service (QoS). Different CoS components are used to achieve these goals. Let's analyze each option to determine which CoS component allows you to alter class-of-service values on the outbound interface of an edge router.

1. **Output Policer**:

- Policing is used to control the rate of traffic sent to or from a network interface. It can drop or remark traffic that exceeds a certain rate.

- Policing is not typically used to alter CoS values but to enforce traffic limits.

2. **Scheduler**:

- A scheduler is responsible for managing the order in which packets are transmitted out of an interface based on their CoS markings. It can allocate bandwidth and prioritize traffic.

- The scheduler manages how packets are queued and sent but does not alter the CoS values of packets.

3. **Rewrite Rules**:

- Rewrite rules are used to modify the CoS values of packets, such as DSCP (Differentiated Services Code Point) or 802.1p bits, as they exit an interface.

- Rewrite rules can alter the class-of-service values in the packet headers to match the desired policies of the outbound interface.

- Therefore, rewrite rules are the correct component for altering CoS values on an outbound interface.

4. **Forwarding Classes**:

- Forwarding classes are used to categorize packets into different traffic classes within a router for QoS handling.

- They help in defining how packets should be treated by the scheduler but do not directly modify the CoS values.

**Conclusion**:

To alter class-of-service values in packets on the outbound interface of an edge router, the correct CoS component to use is:

**C. rewrite rules**

**References**:

- Juniper Networks Documentation on CoS: [Class of Service Overview](https://www.juniper.net/documentation/en_US/junos/topics/concept/class-of-service-overview.html)

- Junos OS CoS Configuration Guide: [Rewrite Rules](https://www.juniper.net/documentation/en_US/junos/topics/topic-map/class-of-service-rewrite-rules.html)

In the exhibit, we see an internal BGP (iBGP) setup within AS 65512, and an external BGP (eBGP) connection between R3 and ISP-A (AS 65511). The questions focus on the behavior of BGP routes advertised from R3 to R1 within the same AS.

1. **BGP Next-Hop Attribute (Option A and D)**:

- In iBGP, the next-hop attribute is **not** changed when a route is advertised to another iBGP peer. This means that when R3 advertises a route to R1, it retains the original next-hop value as learned from the eBGP peer (ISP-A).

- Therefore, Option D is correct: "By default, the next-hop value for these routes is not changed by R3 before being sent to R1."

2. **BGP Attributes (Option B and C)**:

- BGP attributes such as local preference, AS-path, and others are crucial for BGP route selection. The local preference attribute is used within an AS to indicate the preferred path for outbound traffic.

- When R3 advertises BGP routes to R1, it includes the local preference value assigned to those routes. This value is not removed and is propagated within the iBGP mesh.

- Therefore, Option C is correct: "By default, the BGP local-preference value that is assigned on R3 is advertised to R1."

**References**:

- Juniper Networks documentation on BGP behavior provides detailed insights into the propagation of BGP attributes within iBGP and eBGP contexts. Specifically, the Junos OS documentation covers the default behavior of next-hop and local preference attributes in BGP configurations.

- Junos OS BGP Configuration Guide: [Junos OS BGP Configuration Guide](https://www.juniper.net/documentation/en_US/junos/topics/concept/bgp-overview.html)

- For a deeper understanding of BGP attributes and their default behaviors, the "Juniper Networks Day One: Exploring BGP" book is an excellent resource.

TLVs are tuples of (Type, Length, Value) that can be advertised in IS-IS packets. TLVs can carry different kinds of information in the Link State Packets (LSPs). IS-IS supports both narrow and wide metrics for link costs. Narrow metrics use a single octet to encode the link cost, while wide metrics use three octets. Narrow metrics have a maximum value of 63, while wide metrics have a maximum value of 16777215. If there are both narrow and wide metric devices in the topology, IS-IS will advertise two TLVs for each link: one with the narrow metric and one with the wide metric. This allows backward compatibility with older devices that only support narrow metrics12.