4A0-C02 Questions and Answers

All in-profile packets in round-robin, then all out-of-profile packets in biased round-robin.

In-profile EF packets, then in-profile H2 packets, then in-profile AF packets, then out-of-profile EF packets, then out-of-profile H2 and AF packets, and then out-of-profile BE packets.

In-profile EF, H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF packets, then in-profile H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF and H2 packets, then in-profile AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

2

3

5

6

None of the above.

It is best used when a single VPN is required to provide Internet access, as well as to maintain VPN connectivity between different customer sites.

If there is no requirement for the VRF to contain the full Internet routing table, a default route to the Internet gateway router is sufficient.

Only one interface on the CE is required for both VPN and Internet connectivity.

The Nokia 7750 SR supports route leaking in full mesh and extranet VPRN topologies only.

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

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

MSTP

MCLAG

LACP

DHCP

A proprietary protocol

oam vprn-ping source destination

oam vprn-ping source destination

vprn-ping router

Ping source

3

64

72

16

56

Profile mode queues

Priority mode queues

1 queue

3 queues

3 forwarding classes

1 forwarding class, with 2 subclasses

1 forwarding class, with 3 subclasses

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

Option A

Option B

Option B

Option C

Option E

Bridge B 1/1/3

Bridge B 1/1/2

Bridge C 1/1/2

Bridge C 2/1/1

Bridge D 1/1/1

Bridge D 1/1/3

Bridge E 1/1/1

The solution scales as the number of VPNs offered by the customer carriers increases.

The solution scales as the number of end-customer routes increases.

There is no need to manage end-customer services.

The solution scales as the number of serviced customer carriers increases.

Bridge B 1/1/3

Bridge B 1/1/2

Bridge C 1/1/2

Bridge C 2/1/1

Bridge D 1/1/1

Bridge D 1/1/3

Bridge E 1/1/1

TRUE

FALSE

One Route Distinguisher per VRF route

One Route Distinguisher per VRF

One Route Distinguisher per VRF per site

One Route Distinguisher per VPN

H2

NC

L2

EF

H1

BE

The router will accept the update and send a notification.

The router will not accept the update and send a notification.

The router will accept the update and ignore the attribute.

The router will accept the update and propagate the attribute.

A route received from a BGP peer within the same AS.

A route originated by a router in a different cluster of the same AS.

A route received from a BGP peer from a different member AS of a confederation.

A route received from a BGP peer from the same member AS of a confederation.

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

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

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

LDP labeled routes for all PE system addresses in AS 5000.

the configuration is complete and correct.

'as-override' should be configured under the BGP context.

'as-override' should be configured under the group context.

'as-override' should not be part of this configuration.

PE1 is the master.

The system-ID used by the CE device is 60:2c:ff:00:00:00.

The Admin Key used by the CE device is 40000.

There is a configuration error between the two MC peers.

It is important that all packets are classified in the same way at all SAP-ingress points.

Once a packet is classified to a forwarding class, it cannot change across the network.

Packet enters a node will be treated as per the local hop's configured policy.

Native IP packets entering a network port will be marked at the first network egress by default

Native IP packets entering a network port will not be marked at the first network egress by default.

Native IP packets entering a network port will be marked at the first network egress, regardless of the re-marking configuration.

Simplifies signaling.

Reduces core's forwarding database size.

Simplifies MDU configuration.

Enables a scalable inter-domain solution.

Next Hop is modified when crossing member AS boundaries within a confederation.

Origin Code is modified when crossing member AS boundaries within a confederation.

AS Path is modified when crossing member AS boundaries within a confederation.

None of the well known mandatory attributes is modified within a confederation.

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.

An AS is a set of routers under a single technical administration.

An AS efficiently advertises all IGP known routes to other ASs.

An AS presents a consistent routing policy to other autonomous systems.

An AS has a 2-byte or 4-byte AS number assigned.

PIR

CIR

MBS

burst-limit

VPLS 100 was not actually configured as a management VPLS.

VPLS 10 and VPLS 20 are not actually configured as a user VPLS.

VPLS 10 and VPLS 20 are not using the same spoke-sdps that the management VPLS is using.

Based on the output there is now way of telling if there is a problem with the configuration.

Yes

No

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router

ASBR2 has a total of three BGP sessions established: one with PE2, one with RR2, and one with ASBR1.

RR1 has a total of three BGP sessions established: one with PEL one with RR2, and one with ASBRL

PE2 has a total of two BGP sessions established: one with RR2 and one with ASBR2.

PE1 has a total of two BGP sessions established: one with RR1 and one with PE2.

Show router bgp routes

Show router bgp routes address-family vpn-ipv4

Show router bgp routes

Show router bgp routes

I-VPLS is configured in the core of the network with an l-MAC address. This l-MAC address is the only MAC learned in the core

The B-VPLS and l-VPLS are configured in the edge. The B-VPLS is configured with a Backbone MAC and is the only MAC learned in the core

Each SDP is configured with a Backbone MAC to hide customer MAC addresses in the core

Each SAP is associated with a common l-MAC to hide customer MAC addresses in the core

The EXP field in the bottom MPLS header will be marked.

The EXP field in both the top and bottom MPLS headers will be marked.

For Layer 2 services, the top MPLS header will be marked; for Layer 3 services, the bottom MPLS header will be marked.

The EXP field in the top MPLS header will be marked.

Neither the top nor the bottom EXP field will be marked since EXP remarking can only be done on the network ingress.

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."

TRUE

FALSE

Real-time

Assured

Non-conforming

High priority

In-profile

Reduced number of VPN tunnels that need to be managed

Centralized filtering policies with the introduction of a hub site

Optimal routing between all sites

Limited configuration required on the hub PE device

CSC eliminates the need for customer carriers to build and maintain their own MPLS backbone.

CSC is also known as carrier's carrier or carrier serving carrier.

The customer carrier provides VPN or Internet services to its end-customers.

A CSC VPRN is configured on the customer carrier's CSC-CE routers.

The primary contributors to latency are distance, scheduling, and congestion.

The weighted round robin scheduling algorithm will result in more delay for high priority traffic than the regular round robin algorithm.

The round robin scheduling algorithm will result in less jitter for low priority traffic than a strict priority scheduler.

Packet loss can be reduced by decreasing the amount of buffer space available to a queue.

Latency can be reduced by increasing the amount of buffer space available to a queue.

Service labels are assigned based used on label blocks.

BGP-AD, RADIUS and Management are used for auto-discovery.

Service labels are signaled using MP-BGP.

Hierarchical VPLS is loosely defined in the standards.

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

network

scheduling

slope

SAP-ingress

network-queue

Interfaces, ports, SAPs

Ports, ports, MDAs

MDAs, MDAs, ports

Interfaces, interfaces. MDAs

MDAs, ports, interfaces

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.

9100

9104

9108

9122

9126

TRUE

FALSE

Discovery and auto-negotiation of OAM capabilities.

Link monitoring via event notifications.

Remote failure indication (RFI).

Remote Loopback

Latency and jitter across a service.

It depends if traffic is received via R4 or R1 from devices behind R2.

The devices cannot communicate based on the configuration in the diagram so there will be no mac address association.

Devices behind R2 will be associated with the sdp between R3 and R1.

Devices behind R2 will be associated with the sdp between R3 and R4.

Ring topologies.

Metro-to-metro topologies

H-VPLS topologies.

Partial-mesh topologies.

The same as the number of alternate ports in the topology

1 per segment

The same as the number of root ports

1 per switch

The 1-SID must be explicitly configured.

The 1-SID only supports a range from 1 to 255.

The 1-SID will default to 511 .the value of the service-id.

Thel"SIDwilldefaultto131582, the value of the service-id + 131071.

TRUE

FALSE

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.

10.0.2.1

10.0.2.2

10.16.10.1

10.16.10.3

All BGP routes are rejected.

All BGP routes are accepted.

All routes matching prefix list "List-1" are rejected.

All BGP routes matching prefix list "List-1" are rejected.

Router R1must have at least one BGP session to each of routers R1x and R2x.

Routers R1, RR1 and RR2 must be fully meshed.

Routers R1x and R2x must have at least one BGP session between them.

Routers R1x as well as routers R2x must be fully meshed.

A single route for 192.168.0.0/16 is advertised.

BGP routes 192.168.1.0/27, 192.168.2.0/27, and 192.168.0.0/16 are advertised.

BGP routes 192.168.1.0/27 and 192.168.2.0/27 are advertised, and 192.168.0.0/16 appears as a "Blackhole" route in the route table only.

The given export policy is invalid.

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

Well-known mandatory

Well-known discretionary

Optional transitive

Optional non-transitive

Option A

Option B

Option C

Option D

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

The IPv6 link-local address of the router D interface towards router A.

The IPv6 link-local address of the router A interface towards router D.

The IPv6 global address of router A.

The IPv6 global address of router D.

65206 65202 65100

(65206 65202)65100

(65204 65206 65202) 65100

(65200) 65100

Router R3 only.

Routers R3 and R4 only.

Routers R3, R4 and R5 only.

Router R2 does not advertise an update for the prefix.

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.

Bridge B

Bridge C

Bridge D

Bridge E

The Alcatel-Lucent 7750 SR supports 1:1 mapping of I-VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports 1:1 andM:1 mapping of l-VPLS services to B- VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to l-VPLS services.

Two routes from router R4.

Two routes from router R5.

Two routes; one from router R4 and one from router R5.

Four routes; two from router R4 and two from router R5.

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

Originator_ID of RR1; and Cluster_List of 10.16.10.1.

Originator_ID of RX; and Cluster_List of 10.16.10.1.

Originator_ID of RR1; and the Cluster_List is not set.

Neither the Originator_ID nor the Cluster_List is set.

The entire confederation is viewed as a single AS by an eBGP peer.

Within a confederation, each member AS is considered as a stand-alone AS.

Member ASs within a confederation can use route reflection.

Member ASs must be fully meshed within a confederation.

If the MAC address of this new client device does not reach the upper limit of the configured total number of MAC addresses allowed in the VPLS forwarding database, then the new MAC address will be stored.

The new source MAC addresses will not be entered in the VPLS service forwarding database.

New local source MAC addresses will not be entered in the VPLS service forwarding database, but new remote MAC addresses would continue to be entered.

New remote source MAC addresses will not be entered in the VPLS services forwarding database, but new local MAC addresses would continue to be entered.

This is not a best practice. Any switch can be used as the root bridge.

So that you know which links will be active in your network.

To prevent a new switch from becoming root when added to the network.

To allow all ports on the root switch to become alternate ports.

Multiple SDPs must be configured and bound to the LSPs for this to be possible.

It is not possible to carry multiple services over the same MPLS LSPs.

A vc-label is signaled per service.

The vc-id is part of the data plane and maps the traffic to the appropriate service.

oam mac-ping

oam mac-populate

oamsvc-ping

oam mac-trace

Multicast frames only forward out ports that have a known receiver.

Unicast frames only forward out ports that have a known receiver.

If the FDB is empty, unicast and multicast frames are treated equally.

If the FDB has an entry for the unicast frame, both unicastand multicast are treated equally.

All traffic exchanged between end-customers is carried over a single CSC VRF.

Customer carrier PE routers residing in different sites must run eBGP between them to exchange customers' routes.

The customer carrier network can be a pure IP network.

MPLS can be used in the customer carrier network to improve scalability.

This configuration is correct and complete

This configuration is correct except that the system interface must be added

This configuration is correct except that the interfaces facing the CE routers must be added.

MPLS configuration is not required

There will be increased memory usage on the PE

There will be increased CPU utilization on the PE

The CE will reject the overlapping prefix

The PE will not recognize the prefixes as being different

There is no issue with overlapping address space in a traditional Layer 3 VPN

Participate in service provider core routing

P devices are not required to be MPLS enabled. MPLS is only required on the PE devices

Run a common routing protocol with the CE router

Must support MP-BGP

Do not have any connections to the CE

Must be aware of the VPRNs

"Spoke.Sites" and "Hub_Site"

"Hub_Site"

"Spoke_Sites"

No communities should be imported

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

Allow routes to be exchanged between all or selected sites of one VPRN and all or selected sites of a second VPRN

Allow the service provider to provide multiple VPRNs with Internet access

Reduce the number of VPRN tunnels required

Simplify the administration of multiple VPRNs

Force all traffic in multiple VPRNs to pass through a single device

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.

64496 64497

64496

64497

64497 64497

The SDP path-MTU minus 14

The LMTU found in how router ldp bindings on the VPLS side of the spoke SDP

The configured service-mtu of the VPLS service

The LMTU found in how router ldp bindings on the VPLS side of the spoke SDP minus14

The SDP path-MTU

The configuration is incomplete as the uto-bind command is missing

The configuration is incomplete as the ignaling off command is missing

The configuration is incorrect as VPRN service does not support spoke-sdp configuration using MPLS LSPs

The configuration is incorrect as Line 8 should be poke-sdp 42 mpls create

The configuration is complete and correct