4A0-C03: Nokia NRS II Composite Exam: IS-IS version

An ERO carries explicit-route subobjects that specify the path, not MPLS label bindings. Label bindings are conveyed using the LABEL object in the RSVP RESV message after a LABEL_REQUEST in the PATH message.

One-to-one FRR uses a separate RSVP-TE detour tunnel for each individual primary LSP. A protection tunnel shared by multiple LSPs is a facility-mode bypass tunnel, not a one-to-one detour.

A route-reflector client is an iBGP router. eBGP neighbors can advertise routes to a route reflector, but they are not route-reflector clients; therefore, a route reflector cannot have eBGP clients. Route reflection relaxes the usual iBGP advertisement restriction for client relationships and reduces the need for a full mesh of iBGP sessions within an AS.

On SR OS, a dot1q/QinQ SAP is defined as port:qtag1.qtag2, where a wildcard is permitted for the inner qtag when the outer qtag is explicit, but the outer qtag cannot be wildcarded while the inner tag stays explicit, and a single SAP definition cannot enumerate multiple discrete outer-tag values as alternatives. To accept only frames with outer VLAN 200 combined with inner VLAN 33, and separately outer VLAN 250 combined with inner VLAN 33, two SAPs must be configured — one per outer/inner tag pair — since no single wildcarded SAP expression matches exactly those two combinations without also matching unwanted traffic or missing one of the required outer tags.

A Route Target is a BGP extended community that identifies VPN membership and controls which VPRN/VRF instances import or export a VPN route. Different RT values control route distribution; they do not themselves make overlapping private IP prefixes usable. Prefix overlap is supported by separate VPN/VRF routing contexts and route distinguishers that make otherwise identical VPN route prefixes unique.