4A0-C02 Practice Exam Questions with Answers Nokia SRA Composite Exam Certification

An LSP must be configured between PE-A and PE-D for this traffic to be forwarded.

A VPLS FDB lookup is done at PE-A of Metro A only

An SDP must be configured between PE-A of Metro A and PE-D of Metro D for this traffic to be forwarded

A VPLS FDB lookup is done at PE-A and PE-C of Metro A and PE-B of Metro B

On the PE the endpoint has been configured with "supress-standby-signalling"

On the PE the endpoint has been configured with "no supress-standby-signalling"

On the MDU the endpoint has been configured with "supress-standby-signalling"

On the MDU the endpoint has been configured with "no supress-standby-signalling1

Option A

Option B

Option C

Option D

Authentication is performed before establishing the BGP session.

Authentication can only be configuredon the group or neighbor level.

By default, MD5 authentication is disabled.

Peer authentication may be optionally requested in an open message.

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.

12

13

14

15

The local system has received a Keepalive message and is ready to exchange updates.

The local system is exchanging Update messages with its neighbor.

The local system has sent a Keepalive message to its neighbor and is waiting to receive one back.

The local system has sent an Open message to its neighbor and is waiting to receive one back.

All BGP routes are accepted.

All routes matching prefix lists "List-1" and "List-2" are rejected.

BGP routes matching prefix lists "List-1" or "List-2" are rejected.

BGP routes matching prefix lists "List-1" and "List-2" are rejected.

TTL is a well-known mandatory BGP attribute.

The default TTL value of an eBGP message is 1, and 64 for an iBGP message.

The default TTL value of an iBGP message can be modified using the multihop command.

The default TTL value of an eBGP message can be modified using the "ttl-security" command.

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.

Only the route reflector is configured with a cluster id.

There can only be one route reflector in a cluster.

Clients should have iBGP sessions with each other to maintain the mesh.

There can only be one level of route reflectors in the topology.

There can only be one community associated with a route.

Community is an optional non-transitive attribute.

Community is an optional transitive attribute.

Community is a well-known discretionary attribute.

ARIN

ICANN

RIPE NCC

LACNIC

APNIC

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.

Well-known mandatory

Well-known discretionary

Optional transitive

Optional non-transitive

The routes are in the RIB-In.

The routes are in the Loc-RIB.

The routes are in the RIB-Out.

The routes are not in any of the BGP databases.

The loopback control PDU instructs the remote port to enter loopback mode.

Putting a port in loopback does not affect customer data flow

Both ports must rediscover the OAM capabilities of each other once the port is put back into service.

Both ports must still send Information PDUs to avoid going back to discovery mode.

When a port is in loopback mode, service mirroring will still work if it is a mirror-source or mirror-destination.

All packets, except for information PDUs, are looped back.

Spanning tree will be disabled on the SAP that the PVST BPDU was received on.

The SAP that the PVST BPDU was received on will be disabled to prevent loops.

The spanning tree encapsulation will be dynamically changed to PVST on the SAP the PVST BPDU was received on.

The PVST BPDU will be ignored and 802.1D 2004 BPDUs will continue to be transmitted on the SAP.

The routes from routers R1, R2 and R5.

The routes from routers R1and R2.

The routes from routers R2 and R5.

Two routes are chosen at random and advertised to router R4.

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.

100

250

The IGP cost

None

This configuration is correct and complete.

This configuration is correct, but the interfaces must also be configured in the "configure router mpls" context.

There is no configuration required for LDP in the core network.

This configuration is correct but Targeted-LDP is also required.

AS Path of 65200 65100, Next Hop of router A.

AS Path of 65200 65100, Next Hop of router E.

AS Path of 65100, Next Hop of router A.

AS Path of 65100, Next Hop of router E.

MEP

MAP

MIP

MUP

The route is discarded.

The route is kept in the RIB-In, but marked as an invalid route.

The route is moved to the LOC-RIB, but not marked as a used route.

The route is moved to the route table, but not to the FIB.

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

A queue will be serviced as expedited if all of the forwarding classes mapped to it are expedited, regardless of its configured type.

A queue will be serviced as best-effort if all of the forwarding classes mapped to it are best-effort, regardless of its configured type.

A queue will be serviced as expedited if at least one of the forwarding classes mapped to it is expedited, regardless of its configured type.

A queue will be serviced as expedited if its type is configured as expedited, regardless of the forwarding classes mapped to it.

PE1 pushes an LDP transport label.

CSC-PE1 pops the BGP label and pushes two labels: a VPN label and an MPLS transport label.

CSC-PE2 pops the MPLS transport label and pushes a BGP label.

CSC-CE2 pops the BGP label and pushes an LDP transport label.

Prefix 172.16.0.0/12 longer.

Prefix 172.31.0.0/22 longer.

Prefix 172.31.0.0/23 longer.

Prefix 172.31.0.0/24 exact.

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.

All untagged frames will be dropped.

The source MAC address of a frame with a top tag of 200 and bottom tag of 300 will be populated in VPLS 3.

All frames with more than one tag will be dropped.

The source MAC address of a frame with a single tag of 500 will be populated in VPLS 1.

The source MAC address of a frame with a top tag of 100 will be populated in VPLS 2.

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 enables a BGP speaker to advertise multiple external routes to iBGP peers.

It enables a BGP speaker to advertise its best external route to iBGP peers when the best overall route is internal.

It enables a BGP speaker to advertise its best external route to eBGP peers without an import policy.

It enables a BGP speaker to advertise its best internal route to eBGP peers without an export policy.

Broadcast traffic will be flooded.

If the unicastSA has not been learned in the FDB, the frame will be dropped.

If the unicast DA has not been learned in the FDB, the frame will be dropped.

All traffic will be dropped, including multicast and broadcast.

Broadcast traffic will be dropped.

802.1D2004

802.1D 1998

comp-dot1w

PVST

On all ports on the Alcatel-Lucent 7750 SR.

At the junction of high-speed to low-speed links or at places of traffic aggregation.

At the junction of low-speed to high-speed links or at places of traffic aggregation.

On low-speed WAN links.

Nowhere. Shaping is only performed in hardware and serviced in a round-robin.

Shapeless policing at SAP-ingress only.

Shapeless policing at SAP-ingress and egress.

Biased round robin queuing at ingress only.

Soft shaping at all network interfaces.

Soft shaping at network ingress only.

It is used for loop detection within the same cluster.

It is used for loop detection between clusters.

It is used for loop detection in a confederation.

It is used to identify the route reflectors within an AS.

Three primary paths,

Two primary paths and one backup path.

One primary path and two backup paths.

One primary path and one backup path.

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.

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.

It specifies the maximum rate at which a queue can be serviced.

It specifies the maximum depth of a queue beyond which packets will be dropped.

It specifies the portion of a queue that is taken from the reserved buffer pool.

It specifies the threshold beyond which only in-profile packets will be queued.

It specifies the peak bandwidth that can be attained by the incoming traffic.

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.

140000 200 135000

137000 140000 200 135000

140000 23456 135000

135000 200 140000

Next Hop is modified in iBGP updates.

Origin Code is NOT modified in eBGP updates.

AS Path is modified in eBGP updates.

Local Preference is NOT modified in iBGP updates.

The router must receive several BGP routes to compute a backup path.

BGP FRR can be triggered by BFD.

The backup path can use the same next hop as the primary path.

BGP peer-tracking can be used to improve BGP FRR failure detection times.

VPLS1500 is a user VPLS.

VPLS 1500 is management VPLS.

Spanning tree BPDUs for the management VPLS are tagged.

Spanning tree BPDUs for the management VPLS are untagged.

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

5-one for each service.

2-one in each direction.

10-five in each direction.

None of the above.

The frame is dropped.

The frame is always flooded

The frame is forwarded and MAC learning is automatically disabled.

The frame is discarded if the destination is unknown.

More information is required to determine the fate of this new frame.

The oam mac-ping will fail. The MAC address must be known in the local FDB to be successful.

The request will be flooded and the only response will come from the PE node that has learned the specified MAC address on a local SAP.

The request will be flooded and the CE device with the corresponding MAC will reply.

All nodes will reply because the oam mac-ping is flooded.

9000

1514

1000

100

An additional management VPLS.

Another set of LSPs between PE1 and PE3 and between PE2 and PE4.

Another set of SDPs between PE1 and PE3 and between PE2 and PE4.

Load balancing has to be enabled within the management VPLS.

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.

PE-A must replicate the frame to all devices participating in the VPLS

PE-A must replicate the frame to all PEs within Metro A

PE-A must replicate the frame to all devices in the Metro A

All of the above

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

Configure the local age timer to be larger.

Configure the local age timer to be lower.

Configure the remote age timer to be larger.

Configure the remote age to be lower.

Discovery and auto-negotiation of OAM capabilities.

Link monitoring via event notifications.

Remote failure indication (RFI).

Remote Loopback

Latency and jitter across a service.

The SDP must be configured to use GRE encapsulation.

The SDP must follow the same path as the user's SDP.

The SDP should be configured to use an RSVP signaled transport with fast reroute.

The SDP must be the same as the user's SDP.

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.

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

A Spanning Tree BPDU will be sent across the mesh flushing the FDB table in all devices participating in the VPLS instance.

Stale information will be used within the VPLS instance to forward traffic until the FDB ages out.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. Only MAC addresses associated with the PE that the failure occurred on will be flushed.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. The entire FDB in the VPLS instance will be flushed.

Relearning of the MAC address that was purged can only be done once customer traffic resumes.

Relearning of the MAC address that was purged can only be done with the "oam mac-populate" command.

Customer traffic destined to the MAC address that was purged will be dropped until the MAC address is relearned with the "oam mac-populate" command.

Relearning of the MAC address that was purged can only be done with the "oam mac-register" command.

TRUE

FALSE

A VPLS is a multipoint Layer 2 service.

A VPLS allows multiple customer sites to be connected in a single bridged domain.

A VPLS on a single node requires a SDP.

With an IP/MPLS infrastructure, service providers can provide multiple VPLS services over a common IP/MPLS infrastructure.

The VPLS switches traffic based on MAC address associated to the appropriate SAP.

Option A

Option B

Option C

Option D

Native IP Packets will not be remarked.

Native IP Packets will be remarked.

Packets associated with a VPRN service on an upstream node will not be remarked.

Packets associated with an ES service on an upstream node will be remarked.

In order to mark Layer 2 traffic, sgt-qos will set various ToS bits.

DSCP bits can be set per application, per routing instance.

The DSCP marking stays nc1 for all applications. Only the internal FC is manipulated across different applications.

In order to mark Layer 2 self-generated traffic, network interfaces must be set to dot1Q.

The internal forwarding class for self-generated traffic is set once and applied to the base router and all VPRN instances.

The customer-id in this command is 9000.

The service-id in this command is 9000.

This value 9000 should be unique across the network as a best practice.

The vc-id will be 6 for the service by default.

The egress vc-label will be 9000.

Learning should be disabled on both SAPs connected to the DPI device to prevent FDB instability

A MAC filter should be applied to both SAPs connected to the DPI to limit MAC learning on the port

An IP filter should be applied to both SAPs connected to the DPI to prevent FDB instability

The SAPs connected to the DPI should be configured with the "discard-unknown" feature to limit MAC learning on the port

discard-unknown

mac-move

disable-learning

enable-mac-stability

VLANs 1-4094

VLAN 0

There is not enough information provided

None, this is an invalid configuration

H-VPLS

M-VPLS

PBB

MC-EP

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

512 MB ingress, 512 MB egress

256 MB ingress, 256 MB egress

1 GB dynamically allocated between ingress and egress.

768 MB dynamically allocated between ingress and egress.

768 MB, with a minimum of 256 MB ingress and egress, and an additional 256 MB dynamically allocated.

af11

af12

af31

af33

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.

oam vprn-ping source destination

oam vprn-ping source destination

vprn-ping router

Ping source

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PEL

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

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.

PE-1 must be configured with mesh-SDPs to every node receiving the multicast traffic. There is no way to reduce the replication or bandwidth.

PE nodes in Metro 1 could be configured with mesh-SDPs. PE nodes in Metro 2 would be configured with mesh-SDPs. However, the connection between Metro networks (PE-2 to PE-6) can be configured with a spoke-sdp. This would reduce the replication and bandwidth used on the link between Metro networks. This also reduces the replication required by PE-1.

PE-1 can be configured with spoke-SDPs to every PE node in both Metro networks. This will reduce the bandwidth and replication within the network.

PE nodes in Metro 1 could be configured with spoke-SDPs. PE nodes in Metro 2 would be configured with spoke-SDPs. However, the connection between Metro networks (PE-2 to PE-6) can be configured with a mesh-sdp. This would reduce the replication and bandwidth used on the link between Metro networks. This also reduces the replication required by PE-1.

TRUE

FALSE

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

sap 1/1/1

sap 1/1/1:0*

sap 1/1/1:0

sap 1/1/1:*

The PE sends an LDP control message that flushes all FDB entries in the VPLS instance.

The PE sends an LDP control message that flushes all FDB entries in the VPLS instance that are associated with the PE that detected the failure.

The PE flushes it's local FDB only.

The PE sends an oam service message that flushes all FDB entries in the VPLS instance.

Yes

No

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.

The sdp id is different on the far-end.

LDP is disabled on the far-end.

The vc-id is different on the far-end.

The mesh-sdp is missing on the far-end.

The mesh-sdp is administratively shutdown on PEL

There is an MTU mismatch.

The l-TAG in the l-SID is inspected to determine where the frame should be delivered.

When the B-MAC header is stripped the customer MAC address is then looked up in the FDB

The l-SID in the l-TAG is inspected to determine where the frame should be delivered.

The PE inspects the service label in the MPLS header before stripping the B-MAC header.

The FDB on PE-A will contain entries for all CE routers.

The FDB on PE-B will contain an entry for the CE router connected to PE-A.

The FDB on PE-B will contain an entry for all CE routers.

The FDB on PE-C will contain entries for the CE router connected to PE-A and the CE router connected to PE-C.

MEP

MAP

MIP

MUP

Either a hub and spoke or an extranet VPRN

An extranet VPRN

A hub and spoke VPRN

Either a full mesh or a hub and spoke VPRN

Show service all

Show service id detail

Show service id base

Show service id bindings

Show service sap-using

PE1 advertises 64496:1:192.168.1.0/27 route update to ASBR1.

PE2 advertises 192.168.1.0/27 route update to CE2.

ASBR1 advertises 64496:1:192.168.1.0/27 route update to ASBR2.

ASBR2 advertises 64497:1:192.168.1.0/27 route update to PE2.

PE1 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

ASBR1 sends the data packet with one label: the BGP label.

ASBR1 sends the data packet with one label: the service label.

ASBR2 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

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.

The routes to be shared are identified by common route targets

The routes to be shared are identified by common route distinguishers

The routes to be shared are identified by common AS numbers

The routes to be shared are identified by common VPN labels

The PE will install a maximum of 40 prefixes into the customer vrf and generate a log message when 40 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, and generate a log message both when 30 and 41 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and disable learning of new routes at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and drop the connection at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 4 routes are received and disable learning of new routes at 41

R1-R3-R8

R1-R2-R4-R8

R1-R3-R4-R8

R1-R2-R4-R3-R8

Two primary paths and one backup path.

One primary path and two backup paths.

Three primary path and one backup path,

Three primary paths.

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.

AS Path of 65200, Next Hop of router A, Origin of IGP.

AS Path of 65200, Next Hop of router A, Origin of incomplete.

Null AS Path, Next Hop of router A, Origin of IGP.

Null AS Path, Next Hop of router A, Origin of incomplete.

100

200

300

None

Policy changes are delayed until the peer router with the affected routes reboots.

Policy changes are delayed until route updates for affected BGP routes are received from peers.

Policy changes are delayed until BGP sessions are cleared or BGP is reset.

Policy changes are delayed until the router reboots.

1

2

3

4

Advertising customer networks into BGP.

Sending aggregates that summarize the AS s address space.

Sending MEDs to influence ingress traffic from peers.

Preventing unwanted NLRI from entering the AS.

1

2

3

None

An import policy that rejects updates with an AS Path matching the regular expression ".+ 65540 .+".

An import policy that rejects updates with an AS Path matching the regular expression ".+ 65540".

An import policy that rejects updates with an AS Path matching the regular expression "65540 .+".

An import policy that rejects updates with an AS Path matching the regular expression "65540".

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

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.

R5-R2-R4-R8

R5-R1-R3-R4-R8

R5-R1-R2-R4-R8

R5-R1-R3-R7-R8

Option A

Option B

Option C

Option D

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.

100

The IGP cost

500

None

True

False

192.60.100.0

10.10.10.6

10.10.10.3

192.50.1.1

The routes learned from CE3 and PE1.

The route learned from CE3 only.

The routes learned from PE1 and PE2.

The routes learned from CE3 and PE2.

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

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

An MP-BGP update carries an MPLS label that is used as the service label for a VPRN.

There can be multiple Route Targets per route in an MP-BGP update.

There can only be one Route Distinguisher per route in an MP-BGP update.

On a specific PE, the MP-BGP updates for prefixes from a single VPRN carry different labels.

Traditional BGP attributes and MP-BGP attributes are present in an MP-BGP update.

0

5

10

15

45

On the CE under the OSPF context

On the PE under the BGP context

On the PE under the OSPF context

On the CE under the BGP context

This policy is not required.

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.

RR2 advertises the VPN-IPv4 route update of 192.2.1.0/27 to RR1

RR1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR2

RR2 advertises the VPN-IPv4 route update of 192.1.1.0/27 to PE2

PE1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR1 and ASBRL

PE1 pushes two labels on the IP packet and forwards it to ASBR1.

ASBR1 pops the LDP label, swaps the BGP label and forwards the IP packet to ASBR2.

ASBR2 forwards the IP packet with two labels to PE2.

PE2 pops the labels and forwards the unlabeled IP packet to its destination.

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router

This is the base routing table from CE-1

This is the base routing table from PE-1

This is the customer vrf from CE-1

This is the customer vrf from PE-1D.This is the customer vrf from PE-1

This is the customer vrf from PE-2E.This is the customer vrf from PE-2E.This is the customer vrf from PE-2

This is the base routing table from PE-2F.This is the base routing table from PE-2F.This is the base routing table from PE-2

This is the base routing table from CE-2G.This is the base routing table from CE-2G.This is the base routing table from CE-2

PE1 sends an IPv4 update for prefix 192.168.1.0/27 via MP-BGP to ASBR1.

ASBR1 sends an IPv4 update for prefix 192.168.1.0/27 to ASBR2.

ASBR1 transforms an IPv4 update for prefix 192.168.1.0/27 to a VPN-IPv4 route; allocates VPN label V1 and sends the update to ASBR2.

ASBR2 accepts a VPN-IPv4 update from ASBR1, then sends the update to PE2 via MP-BGP.

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

When the route is first received at the P from the PE

When the route from the CE is populated into the VRF at the PE

When the route from the PE is populated into the VRF at the CE

When the route is propagated from the PE to the CE

When the route is exported into the MP-BGP table from the VRF

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

When the P receives the route from the PE.

When the PE populates the route received from the CE into the VRF.

When the PE propagates the route to the CE.

When the PE exports the route from the VRF into the MP-BGP table.

"Extranet-VPN-Blue" and "Extranet-VPN-Green"

"Blue-Only"

"Extranet-VPN-Blue"

"Blue-Green"

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

The SoO attribute can be used to uniquely identify the site from which a PE learns routes.

Before a PE redistributes a VPN-IPv4 route, it can assign an SoO attribute to the route.

The SoO attribute can be used to prevent loops from a single site with multiple CE-PE connections.

The SoO attribute can be used as matching criteria when redistributing routes from the CE to the PE.

PE2 pushes one label on the IP packet and forwards it to ASBR2.

ASBR2 forwards the IP packet with one label to ASBR1.

ASBR1 forwards the IP packet with two labels to PEL

PE1 forwards an unlabeled IP packet to CE1.

Router R1

Router R2

Routers R1 and R2

Router R3

Router R4

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

PE1 and PE2 advertise the same VPN route to the route reflector.

The route reflector receives two routes for prefix 10.1.1.0/24; one from PE1 and one from PE2.

The route reflector reflects two routes for prefix 10.1.1.0/24.

PE3 receives two routes and is able to load balance traffic across PE1 and PE2.

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.

The protocol is configured under the config>service context

The protocol is configured under the global router context

The interface leading to the PE is defined as a protocol neighbor

The routing protocol used must be the same as the routing protocol used at other CE-PE locations in the same VPN.

A routing policy may or may not be required depending on the routing requirements and routing protocol

RSVP-TE has signaled a VPRN label.

RSVP-TE has signaled both VPRN and LSP labels.

MP-BGP has signaled both VPRN and LSP labels.

MP-BGP has signaled a VPRN label.

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.

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

It is an 8 byte value containing 3 fields

The Route Distinguisher must have the same value as the Route Target.

The Administrator field contains either an AS number or an IP number

To ensure uniqueness, Route Distinguishers are assigned by the IANA.

The Route Distinguisher is not used if the customer addresses do not overlap

The Assigned Number field must contain a public IP address

To limit the number of routes advertised from a customer site

To limit the number of routes learned from other customer sites CTo limit the size of the VRF table

To limit connectivity to selected customer networks

To perform packet filtering

MP-iBGP sessions must be configured between the PE routers in each AS.

LDP must be configured in each AS.

MP-eBGP sessions must be configured between the ASBRs.

The ASBRs must be configured with "enable-inter-as-vpn".

The AS-Path is not present because a policy is configured on PE2 to set it to null.

The AS-Path is not present because a policy is configured on CE1 to set it to null.

The AS-Path is not present because a policy is configured on PE1 to set it to null.

The AS-Path is not present because VPN-IPv4 routes do not propagate the IPv4 AS-Path BGP attribute.

Global, router

Router, router

Service, router

Router, service

Service, service

Router, global

The route update sent from PE1.

The route update sent from PE2.

The route update sent from ASBR1.

The route update sent from ASBR2.

Uses standard Ethernet dot1q and QinQ encapsulation.

Requires IS-1S as the protocol to carry control information.

Ethernet Ring APS is a defined ITU standard.

Standard Ethernet forwarding, learning, and flooding rules apply.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

The default forwarding class defined in the SAP-egress policy.

The forwarding class inherited from network ingress classification.

Best Effort.

If there is no match, packets will be dropped.

Shaping does not add latency.

Shaping does not add jitter.

Shaping protects downstream nodes from traffic bursts.

Shaping requires less memory to buffer packets.

1 multipoint and 8 unicast.

8 queues, regardless of traffic type.

8 unicast and 24 multipoint.

8 unicast and 8 multipoint.

16 queues, distributed as desired.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

8

16

6

4

3

The larger the configured MBS value, the lower the amount of shaping performed.

When policing is enabled on the SAP-ingress, all traffic is considered as in-profile.

Setting the CIR to 1000 and the PIR to max will enable shapeless policing at 1 Mbps within the SAP-egress policy.

Configuring MBS to equal CBS will disable shaping.

Setting the CIR and PIR to equal values disables soft-policing.

Those marked with dotlp = 5.

Those marked with dscp = "ef.

All packets mapped to queue 6 have the same priority to use the available buffer space.

There are no packets mapped to Queue 6.

AF

EF

H2

H1

BE

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.

All buffer space is initially allocated to access pools, and some of it is reallocated to network pools if network interfaces are configured on it.

All buffer space is initially allocated to network pools, and some of it is reallocated to access pools if service SAPs are configured on it.

Buffer space is allocated 50% for access pools and 50% for network pools.

Buffer space is allocated 25% for access pools and 75% for network pools.

The IOM3 adds more memory to both forwarding complexes which increases the total number of queues available.

The IOM3 only contains a single forwarding complex which reduces the number of queues used.

The IOM3 allows multiple forwarding classes to be assigned to a single queue.

The IOM3 allows queues to be dynamically allocated between ingress and egress.

The IOM3 has a larger CPU capable of tracking active hardware queue utilization and adjusting memory allocation accordingly.

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.

The DSCP marking stays ncl for all applications; only the internal forwarding class is manipulated across different applications.

DSCP bits can be set per application, per routing instance.

The internal forwarding class for self-generated traffic is set once and applied to the base router and all VPRN instances.

Self-generated traffic can be marked at Layer 2 no matter what encapsulation is used on the network interfaces.

The NRLI

The AFI

The SAFI

The extended community

Classification

Marking

Queuing

Congestion management

Scheduling

The DSCP value will be set to af21.

The DSCP value will be set to af23.

The DSCP value will remain as ef.

The EXP value, in the MPLS headers, will be set to 4.

The EXP value, in the MPLS headers, will be set to 3.

Using dot1p bits of the 802.1q Ethernet frame header

Using DSCP bits within the ToS field of the IP packet header.

Using the IP precedence bits within the ToS field of the IP packet header.

Using the CLP bit of the ATM cell header.

Using the EXP bits of the MPLS transport label header.

True

False

EF

H1

L1

H2

L2

BE

AF

EF

H1

Simplifies signaling.

Reduces core's forwarding database size.

Simplifies MDU configuration.

Enables a scalable inter-domain solution.

A standalone policer has no parent arbiter, while a CFHP pohlicer has a parent arbiter.

A standalone policer has a fixed PIR rate, while a CFHP poker's PIR rate can be dynamically adjusted by its parent arbiter.

Both standalone and CFHP policers use the FIR bucket to gain access to their fair share of the available bandwidth.

Both standalone and CFHP policers use a policer output queue to store packets before they are forwarded.

TRUE

FALSE

MAC learning

SA filtering

Routing table population

Frame forwarding

The slope-policy

The SAP-ingress policy

The SAP-egress policy

The network-queue policy

The scheduler-policy

Link LDP or MP-BGP

Link LDP or RSVP-TE

T-LDP or MP-BGP

T-LDP or RSVP-TE

DSCP is part of the Layer 3 header.

DSCP is a 6-bit field.

DSCP specifies eight different priorities.

DSCP specifies four precedence levels.

DSCP is part of the Layer 2 header

DSCP specifies 128 different per-hop behaviors.

DSCP

PREC

Dot1p

ToS

Q-in-Q

Each network egress port receives its own buffer pool.

Each SAP-egress port receives its own buffer pool.

All SAP-ingress ports on the same MDA share a buffer pool.

All the network ingress ports on the same MDA share a buffer pool.

Each network ingress port on the same MDA receives its own buffer pool.

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

64

8

3

16

1