4A0-C02 Sample Questions Answers

The DSCP value will be set to af21.

The DSCP value will be set to be.

TheDSCPvaluewillbesettoaf23.

The DSCP value will be set to af 12.

Thedot1pvaluewillbesetto5.

Thedot1pvaluewillbesetto2.

The dot1p value will be set to 3.

QoS is not configured on the router.

Packets in forwarding classes "be" and "12" are being queued.

Traffic belonging to forwarding class "ef" is not experiencing queuing delays.

Traffic belonging to forwarding class "11 "will never make use of the shared buffer pool.

Out-of-profile traffic in the shared buffer pool is being dropped.

802.1p adds 16 bits to the Layer 2 header,

802.1p adds 16 bits to the Layer 3 header.

802.1p specifies 64 different priority levels.

802.1p uses a field in the 802.1Q header.

802.1p uses a field in the Layer 3 IP header

802.1p defines a 3-bit Class of Service field.

The individual SAPs and SDPs will age out MAC addresses for this VPLS.

Aging will be disabled for locally-learned MAC addresses for this VPLS.

Aging will be disabled for both local and remote MAC addresses for this VPLS.

Aging will be disabled for remote MAC addresses for this VPLS.

All AF traffic will be marked "in-profile" at the SAP-ingress.

All TCP traffic will be mapped to forwarding class EF.

UDP traffic is placed in queue 3 while ICMP traffic is placed in queue 5.

EF traffic will receive higher scheduling priority than H2 traffic.

Traffic that does not match any of the IP criteria will be placed in queue 3.

1

2

3

4

5

8

Packets can be classified into 16 different FCs when using priority mode queuing.

This feature is available on egress SAPs within any service.

MPLS EXP bits can be changed based on multi-field classification.

If a Behavior Aggregate (BA) and Multi-field (MF) match occurs, only the MF override parameters will take effect.

If a Behavior Aggregate (BA) and Multi-field (MF) match occurs, the BA classification can override the forwarding class while the MF classification can override the profile.

The NRLI

The AFI

The SAFI

The extended community

All untagged frames will be dropped.

All frames with more than one VLAN tag will be dropped.

A frame with an outer VLAN tag of 200 and inner VLAN tag of 300 will be forwarded to VPLS 3.

A frame with a single VLAN tag of 500 will be forwarded to VPLS 1.

A frame with an outer VLAN tag of 100 will be forwarded to VPLS 2.

MAC learning

SA filtering

Routing table population

Frame forwarding

CIR

CIR level

CIR weight

Rate

Level

Weight

The scheduler will be allocated its "within CIR" bandwidth before all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at all levels have received their "within CIR" bandwidth.

The scheduler will not be allocated its "within CIR" bandwidth.

010011

100010

010001

001100

010010

It will be queued in the reserved portion of the buffer pool and remain out-of-profile.

It will be queued in the reserved portion of the buffer pool if there are no in-profile packets already in the queue.

It will be queued in the reserved portion of the buffer pool and be in-profile.

It will be queued in the shared portion of the buffer pool but contend for shared buffer space with packets from other queues.

It will be queued in the shared portion of the buffer pool but may be dropped if the buffer utilization exceeds the start-average value of the low slope.

It will be discarded because the high-priority-only threshold is exceeded.

It will be queued but re-marked as "out-of-profile."

It will be queued in the reserved portion of the buffer pool and remain "in-profile."

It will be queued in the shared portion of the buffer pool but contend for shared buffer space with packets from other queues.

It will be queued in the shared portion of the buffer pool but may be dropped if the buffer utilization exceeds the start-average value of the low slope.

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as "discard eligible."

8

16

6

4

3

Has the ability to distinguish traffic in 32 different ways.

Uses the RSVP protocol to create microflows through a network.

Has the ability to manually configure foiwarding classes through a network.

Uses the RSVP protocol to create macroflows through a network.

TCP port numbers

LSP EXP

DSCP

Source and destination IP addresses

Dot1p priority

Defining the slope of the TCP slow-start mechanism for self generated traffic.

Defining the slope of the scheduling rate per forwarding class when using HQoS.

Defining the high and low slope values when deploying buffer admission control for UDP traffic in the committed buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the shared buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the committed buffer pool.

Real-time

Assured

Non-conforming

High priority

In-profile

It is located in an Autonomous System directly connected to this router

There is a single Autonomous System between the local AS and the AS that originated the prefix

There are two Autonomous Systems between the local AS and the AS that originated the prefix

There may be two or more Autonomous Systems between the local AS and the AS that originated the prefix

It is located in Autonomous System 65100

When sites of different VPRN customers use the same BGP AS number

When sites of the same VPRN customer use the same BGP AS number

When sites of different VPRN customers use different BGP AS numbers

When sites of the same VPRN customer use different BGP AS numbers

When the customer site AS number is the same as the provider AS number

By using the MED attribute to carry the OSPF metric.

By defining Extended Communities for use as the Route Target

By using the Cluster List attribute to carry the network prefix

By defining support for the VPN-IPv4 address family

By adding an additional field to the BGP Update to carry the VPRN label

A

B

C

D

T-LDP and LDP sessions with the other VPRN PE routers and the VPLS PE router

T-LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers, and both T-LDP and LDP sessions with the VPLS PE router

T-LDP and LDP sessions with the other VPRN PE routers and LDP sessions with the VPLS PE router

Distributing customer routing information between sites

Forwarding customer data packets

Providing an integrated billing solution

Maintaining separation between distinct customer networks

Allowing the implementation of Layer 3 devices in the provider core

ample Policy should be applied as an export policy on the PE connected to the main site of Customer 1

ample Policy 3 should be applied as an export policy on the PE connected to the main site of Customer 2

ample Policy 3 should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on all PEs connected to sites of Customer 1

Five routes: the local route, the two BGP routes learned from the local CE, and two tunneled routes.

Six routes: the local route, the two BGP routes learned from the local CE, and three tunneled routes.

Two routes: the local route and one tunneled route.

Three routes: the local route and two tunneled routes.

Two routes: the local route and one BGP route learned from the local CE.

In the routing updates exchanged from CE to PE

In the routing updates exchanged from PE to PE

In the routing updates exchanged from P to PE

In customer packets as they traverse the provider core

In all route tables of the VPRN control plane

Logical Partitioning of route reflectors works best when PEs are partitioned to support different VPRNs.

Logical Partitioning of route reflectors is simple and scalable, but requires more hardware.

Filtering at route reflectors requires either inbound filtering at the route reflector or outbound filtering at the PE routers.

Filtering at route reflectors allows the route reflector to filter routes received from PEs and only accept routes with a certain route distinguisher.

A 64-bit Route Target followed by a 32-bit IPv4 address.

A 64-bit Route Distinguisher followed by a 32-bit IPv4 address.

A 32-bit Route Distinguisher followed by a 32-bit IPv4 address.

A 32-bit Route Target followed by a 32-bit IPv4 address.

Show service 3

Show service id 3

Show service 3 base

Show service id 3 base

Show service 3 detail

Show service id 3 detail

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000

PE1

PE2, PE3 and PE4

PE1, PE2, PE3 and PE4

This command is not required for the configuration of this PE hub and spoke VPRN.

Show service id base

Show router bgp routes

Show service id maximum-routes

Show router status

This approach is recommended when multiple sites advertise the same prefix.

This approach limits the opportunities for load balancing.

This approach requires additional memory on the PEs to store more routes.

This approach is recommended for extranet VPN.

In the CSC VPRN, configure an eBGP session between CSC-PE and CSC-CE and use the "advertise-label vpn-ipv4" CLI command to enable the advertisement of VPN-IPv4 routes.

When the customer carrier uses the same autonomous system number in various sites, use the "loop-detect off" CLI command to disable the loop detection functionality on CSC-CE and PE routers.

On the CSC-PE routers, use the "carrier-carrier-vpn" CLI command to configure the VPRN service as CSC.

Configure an iBGP session between PE1 and PE2 and use the "family vpn-ipv4" CLI command to directly exchange end-customer routes learned from CE1 and CE2.

The route-distinguisher value must be 64496:10 for successful VPRN operation.

An export policy is not required for successful VPRN operation.

The "family vpn-ipv4" command is required under the BGP configuration for successful VPRN operation.

The neighbor address should be 10.10.10.4 under the BGP configuration for successful VPRN operation.

The VPRN configuration on ASBR1 is correct.

Targeted-LDP

BGP

MP-BGP

RSVP-TE

To reduce the number of VPRN tunnels required.

To allow routes to be exchanged between all, or selected, sites of one VPRN, and all, or selected, sites of a second VPRN.

To simplify the administration of multiple VPRNs.

To allow network access between the headquarter sites of each VPRN service and a shared VPRN service offered by a third party.

OSPF is not configured on the CE router

There is a problem with OSPF authentication

The operational MTU does not match

The PE and CE router have different OSPF interface types configured

None of the above

On the CE under the RIP context

On the PE under the BGP context

On the PE under the RIP context

On the CE under the BGP context

This policy is not required

ASBRs exchange labeled IPv4 routes for the system addresses of PE routers.

It requires a route reflector to be configured in each AS for successful operation.

VPN-IPv4 routes are neither maintained nor distributed by the ASBRs.

PE routers in different ASes exchange VPN-IPv4 routes directly between each other using MP-eBGP.

Open

Update

Route Refresh

Notification

If no import policy is specified, all valid BGP routes are passed to the BGP route selection process.

If no export policy is specified, all non-BGP routes are populated into RIB-Out.

If no import policy is specified, all BGP routes are populated into the route table.

If no import policy is specified, only valid BGP routes are populated into RIB-Out.

70 seconds

25 seconds

20 seconds

30 seconds

Only the first route will appear in the RIB-In.

Only the second route will appear in the RIB-In.

Only the third route will appear in the RIB-In.

All routes will appear in the RIB-In.

Route-Refresh

OpenSent

Notification

Update

Keepalive

The first BGP route.

The second BGP route.

Both routes are used.

It is impossible to determine without the value of the origin code for both routes.

All routers with which it has a BGP session.

All routers with which it has a BGP session, except the router it received the update from, which is router B.

All routers with which it has a BGP session, except the router it received the update from, which is router C.

All routers with which it has a BGP session, except the router it received the update from, which is router D.

Only eBGP neighbors.

A single connection to a single service provider.

Two connections to a single service provider.

Two connections to two different service providers.

Multiple connections to different service providers.

ISP 1 and ISP 2 have a public transit relationship, while ISP 3 and ISP 4 have a private transit relationship.

ISP 1 and ISP 2 have a private transit relationship, while ISP 3 and ISP 4 have a public transit relationship.

ISP 1 and ISP 2 have a private peering relationship, while ISP 3 and ISP 4 have a public peering relationship.

ISP 1 and ISP 2 have a public peering relationship, while ISP 3 and ISP 4 have a private peering relationship.

Advertising external networks into IGP.

Using system addresses for setting up iBGP sessions.

Exporting the networks associated with the external links of eBGP peers into BGP.

Optimizing BGP route table by exporting IGP routes into BGP.

Option A

Option B

Option C

Option D

The route is ignored.

The route is flagged as invalid and placed in the LOC-RIB.

The route is flagged as invalid and placed in the RIB-In.

The route is flagged as invalid and placed in the RIB-Out.

Prefix 192.168.0.0/17 longer.

Prefix 192.168.0.0/19 longer.

Prefix 192.168.96.0/19 longer.

Prefix 192.168.0.0/18 longer.

They are allocated to the RIRs by ICANN/IANA.

They are used when connecting ASs on the Internet.

They range from 1 to 56319.

They are assigned by the ISPs for enterprise networks.

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

Option A

Option B

Option C

Option D

ISP 1 has a peering relationship with ISP 2 and ISP 4.

ISP 1 has a peering relationship with ISP 2 and a transit relationship with ISP 3.

ISP 1 has a peering relationship with ISP 2 and ISP 3.

ISP 1 has a transit relationship with ISP 2 and ISP 4.

ISP 1 has a transit relationship with ISP 2 and a peering relationship with ISP 3.

The BGP router that originates an update sets the Originator_ID.

The Originator_IDis set to the ClusterJD of the advertising router reflector.

Both confederation and route reflector topologies use the Originator_ID.

A BGP router ignores an update that contains its own BGP router ID as Originator_ID.

BGP Fast Reroute is triggered by IGP events.

The backup path is pre-computed and installed in the FIB.

BGP Fast Reroute is independent of number of affected prefixes.

BGP Fast Reroute uses the optimal path to the destination.

1

2

3

4

Option A

Option B

Option C

Option D

A confederation is a collection of Autonomous Systems advertised as a single AS number to BGP speakers outside the confederation.

Each member AS must either maintain a full mesh of iBGP sessions, or use route reflection.

Confederations can be used to subdivide ASs that have a large number of BGP speakers into smaller domains.

A full mesh of intra-confederation eBGP sessions is required between the member ASs.

With the same method and attribute as 16-bit AS numbers.

With the same method as 16-bit AS numbers, but using the AS4_Aggregator attribute.

Aggregation is not yet supported with 32-bit AS numbers.

By using a dummy value of 23456 in the 16-bit AS aggregator field. This value lets the router know it needs to read the 32-bit AS number that is contained in the nextTLV.

The update is sent to router R2 in ISP 1.

The update is sent to routers R2 and R3 in ISP 1.

The update is sent to all routers in ISP 1.

The update is sent to routers R2 and R3 in ISP 1, and to router R3 in ISP 2.

An update message is used. Only a single prefix can be withdrawn at a time.

An update message is used. Multiple prefixes can be withdrawn at a time.

A withdraw message is used. Only a single prefix can be withdrawn at a time.

A withdraw message is used. Multiple prefixes can be withdrawn at a time.

It flushes the local FDB speeding recovery

It discards all packets in the queue and sends icmp-discad messages to the sender. The packets are re-transmitted resulting in no loss of data.

On failure, the PE sends an LDP flush-all-from-me message to all PE devices in the VPLS. This speeds convergence to the new topology.

It is not important to use send-flush-on-failure as Active/Standby signalling automatically converges the FDB in all VPLS instances

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

PE-B will require a SAP id of "sap 1/1/1:500*".

PE-B will require a SAP id of "sap 1/1/1:100*".

PE-B will require a SAP id of "sap 1/1/1:500.200".

PE-B will require a SAP id of "sap 1/1/1:200*".

Event notification.

Loopback control.

Information.

Variable request.

Variable response.

Configure a mesh-sdp between all existing PE routers and the new PE router

Configure a mesh-sdp between PE-C and PE-D

Configure a spoke-sdp between PE-C and PE-D.

It is not possible to meet the design requirements.

9100

9104

9108

9122

9126

A management VPLS carries customer traffic over the non-blocking spoke-SDP

A VPLS service must be defined as a management VPLS upon creation to take on the role of a management VPLS

The state of a spoke-SDP within a user VPLS will take on the state of the spoke-sdp within the management VPLS.

The management VPLS must be created before the user VPLS.

Dot1Q

Null

Q-in-Q

Ipcp

BCP

The lower the age-time, the greater the amount of flooding

The higher the age-time, the greater the amount of flooding.

The lower the age-time, the lower the amount of flooding.

There is no relationship between the age-time and the amount of flooding.

ports must be on the same MDA

ports must have the same speed and duplex settings

auto negotiation must be on

auto negotiation must be off or limited

port must be in access mode only

The MDU does not need to support MPLS.

Can be used in ring networks of 4 or more nodes

Does not require the use of a layer 2 loop prevention protocol such as RSTP

The MDU does not have to be aware of the active/standby configuration

Bandwidth and replication inefficiency can occur on inter-metro links if there is a lot of multicast traffic

The number of control sessions grows exponentially in a fully meshed network.

Spanning-tree is required to prevent loops when using mesh SDPs on the inter-metro links.

Network touches increase with each node added to the mesh.

9100

9104

9108

9122

9126

The switch with the lowest priority becomes the root.

The switch with the highest priority becomes the root.

The switch with the lowest MAC address always becomes the root.

The switch with the highest MAC address always becomes the root.

0

1

2

3

oam mac-populate

oam mac-ping

oam mac-trace

oam svc-ping

oam cpe-ping

Spanning-tree BPDUs are returned to the sender.

The MEP sees its own CFM frames returned to itself.

This is not a function of IEEE 802.lag but of 802.1D

The record field of the CFM frame keeps track of chassis-mac addresses.

VLANs 1-4094

VLAN 0

There is not enough information provided

None, this is an invalid configuration

The I-SID is set to 0 by default and is only used for interop purposes. The receiving PE uses the service label to determine the I-VPLS.

There is no default value. The I-SID must always be explicitly configured

The I-SID is set to the service-id, unless the service-id is larger than a 24 bit value. In this case the I-SID must be explicitly configured.

The I-SID is always set to the service-id by default.

Only R4 will be reachable through the VPLS.

B All devices will be reachable through the VPLS.

R4 and R3 will remain reachable.

No devices will be reachable.

The PE devices participating in the VPLS mesh run a separate Spanning Tree instance in the Core. The Primary Bridge is the Root Bridge for the VPLS mesh.

The PE devices participating in the VPLS mesh determine which bridge is closest to Root Bridge. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge has the lowest bridge-id. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge is the Root Bridge. This becomes the Primary Bridge.

TRUE

FALSE

In a dynamic environment where MAC addresses are changing rapidly, the lower the age-time, the larger the fdb-table-size should be.

In a dynamic environment where MAC addresses are changing rapidly, the higher the age-time, the larger the fdb-table-size should be.

In a dynamic environment where MAC addresses are changing rapidly, the higher the age-time, the smaller the fdb-table-size should be.

There is no relationship between the age-time and the fdb-table-size.