H12-821_V1.0 Exam Dumps - HCIP-Datacom-Core Technology V1.0

Comprehensive and Detailed Step-by-Step Explanation:

1. BGP Attributes Overview:

BGP uses attributes to describe the properties of routes. These attributes are classified into the following categories:

Well-Known Mandatory : Attributes that must be recognized and included in every BGP update. Examples: AS_PATH, ORIGIN, NEXT_HOP.

Well-Known Discretionary : Attributes that must be recognized but are not required in every BGP update. Examples: LOCAL_PREF, ATOMIC_AGGREGATE.

Optional Transitive : Attributes that may or may not be recognized, but must be passed along to other BGP peers. Examples: COMMUNITY.

Optional Non-Transitive : Attributes that may or may not be recognized, and are not passed along to other BGP peers. Examples: MED (Multi-Exit Discriminator).

2. Analysis of Each Option:

Option A: Atomic_Aggregate

Correct .

This is a well-known discretionary attribute. It indicates that the advertised route is an aggregate route that summarizes multiple specific routes.

Option B: Local-Preference

Correct .

This is a well-known discretionary attribute. It is used within an AS to prioritize routes, with higher values being preferred.

Option C: Community

Incorrect .

The COMMUNITY attribute is an optional transitive attribute. It is used to tag routes with specific labels to apply routing policies.

Option D: MED (Multi-Exit Discriminator)

Incorrect .

The MED attribute is an optional non-transitive attribute. It is used to influence the choice of the preferred path when there are multiple entry points into an AS.

3. Summary:

Well-Known Discretionary Attributes : Atomic_Aggregate and Local-Preference.

The Forwarding Information Base (FIB) is derived from the router ' s routing table and contains the exact forwarding entries used to route packets. It directly guides packet forwarding decisions by matching incoming packets with the correct output interface or next-hop address ​.

By default, BGP does not automatically summarize imported routes. Route summarization must be explicitly configured using the summary or similar commands ​.

ï‚· Export Routing Policy Changes

When an export routing policy is modified, BGP does not automatically resend affected routes. Manual intervention, such as a clear ip bgp command, is required to resend Update messages reflecting the new policy.

ï‚· Incorrect Options

B. IGP routes can also be advertised into BGP using redistribution, not just the network command.

C. A router can be configured with multiple BGP processes using different AS numbers (multi-instance BGP).

D. Open messages carry additional parameters such as AS number, Hold Time, and Router ID, not just the header.

ï‚· HCIP-Datacom-Core Reference

BGP policy and update behavior are detailed in the route control and redistribution chapters​​.

The Origin attribute in the display bgp routing-table output is marked as i , indicating that the route was injected into the BGP routing table using the network command. The other options are incorrect because the AS path is not displayed, the MED is 0 , and the route is marked as the best ( > ), meaning it is the optimal route ​.

After Layer 3 roaming, the STA’s traffic is forwarded from the Foreign AP (FAP) to the Foreign AC (FAC), and then to the Home AC (HAC) before reaching the upper-layer network. This ensures that the STA remains on the same subnet without breaking existing sessions ​.

ï‚· Edge Port Behavior

An edge port transitions directly to the Forwarding state but reverts to participating in RSTP calculations if it receives a valid configuration BPDU. Thus, statement C is false.

ï‚· HCIP-Datacom-Core Reference

The behavior of edge ports and their transitions are discussed in the RSTP enhancement sections​​.