Refer to the Exhibit.

In the exhibit, the route 66.129.237.5 belongs to a Web server within AS 344.

If you view the AS-path attribute of this route on a router in AS 9021, what will it be?

A.
344 11 221 6044

B.
221 6044 11 344

C.
9021 221 6044 11 344

D.
221 6044 11 344 9021

Explanation:
BGP AS Path Attributes

AS-path attributes are used to provide route metrics. Along with the NLRI information are path attriutes. Path Attributes allow BGP to make determinations of what is the best path. There are several categories that Path Attributes fall into:

WELL KNOWN, MANDATORY
This attribute MUST appear in every UPDATE message. It must be supported by all BGP software implementations. If a well-known, mandatory attribute is missing from an UPDATE message, a NOTIFICATION message must be sent to the peer.
Examples:
* AS_path
* ORIGIN
* NEXT_HOP
WELL KNOWN, DISCRETIONARY
This attribute may or may not appear in an UPDATE message, but it MUST be supported by any BGP software implmentation.
Examples:
* LOCAL_PREF
* ATOMIC_AGGREGATE
OPTIONAL, TRANSITIVE
These attributes may or may not be supported in all BGP implementations. If it is sent in an UPDATE message, but not recognized by the receiver, it should be passed on to the next AS.
Examples:
* AGGREGATOR
* COMMUNITY
OPTIONAL, NON-TRANSITIVE
May or may not be supported, but if received, it is not required that the router pass it on. It may safely and quietly ignore the optional attribute.
Examples:
* MULTI_EXIT_DISC
* ORIGINATOR_ID
* Cluster List