CCNP Practice Question: Router bgp 65000 bgp router-id 10.0.0.1 neighbor…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Routes received from 10.0.0.2 are tagged with community 100:200, but the community is not sent to other BGP peers unless send-community is configured.

  Why this is correct

  This is correct because the route-map 'bgp' is applied inbound from neighbor 10.0.0.2, and it sets the community 100:200 on all received routes. However, BGP does not include community attributes in updates to other peers unless the neighbor is explicitly configured with the send-community parameter. Without send-community, the routes are advertised but the community attribute is stripped, so it never propagates beyond the local router.

• ✗

  Routes received from 10.0.0.2 are tagged with community 100:200 and automatically sent to all neighbors.

  Why it's wrong here

  It assumes the community attribute is automatically included in BGP updates to all neighbors. In Cisco IOS, communities are only advertised when the neighbor is configured with send-community (or send-community extended for extended communities). Without that configuration, the route will be sent to other peers, but the community 100:200 will be removed from the attribute list, so it cannot be seen by remote ASes.

• ✗

  The route-map is applied to outbound updates to 10.0.0.2, setting community on routes sent to that neighbor.

  Why it's wrong here

  This misinterprets the direction of the route-map. The 'in' keyword in the neighbor 10.0.0.2 route-map bgp in clearly indicates that the route-map is applied to inbound updates received from that neighbor, not outbound. Therefore, it does not set community on routes sent to 10.0.0.2; it sets the community on routes coming from 10.0.0.2, affecting how they are treated in the local BGP table and subsequent advertisements.

• ✗

  The configuration is invalid because the community must be a string, not a numeric value.

  Why it's wrong here

  This is false because BGP community values are commonly expressed in the AA:NN format, where AA and NN are 16-bit numbers ranging from 0 to 65535. Numeric communities like 100:200 are perfectly valid and widely used; they are not required to be strings. The configuration is not invalid on this basis—the only potential issue would be missing send-community for propagation, not the format itself.