4A0-C02 Exam Dumps - Nokia SRA Composite Exam

TRUE

FALSE

64

8

3

16

1

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

Link LDP or MP-BGP

Link LDP or RSVP-TE

T-LDP or MP-BGP

T-LDP or RSVP-TE

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.

Operates in transparent mode.

Carries RSTP BPDUs only.

Assigns RSTP state to other VPLS services.

Allows load balancing among multiple management VPLS instances.

64496 – 64511

1 – 56319

64512-65534

64513-65535

There are no defined private AS numbers; there are only private IP addresses.

"client2" routes will be only tagged with communities 'East'' and "South".

"client2" routes will be tagged with community "East".

"client2" routes will only be tagged with community "South".

"client2" routes will be rejected.

Both neighbors R1and R2 should be part of AS 65540.

Neighbor R1should be part of AS 65550, while neighbor R2 should be part of AS 65540.

Neighbor R1should be part of AS 65550, while neighbor R2 should be part of AS 65560.

Both neighbors R1and R2 should be part of AS 65560.

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

32

64

255

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 must be enabled within the VPLS.

Spanning tree BPDUs must be untagged.

Spanning tree BPDUs must be tagged.

Spanning tree must be disabled within the VPLS.

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.

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

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.

Two primary paths and one backup path.

One primary path and two backup paths.

Three primary path and one backup path,

Three primary paths.

Option A

Option B

Option C

Option D

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

100

250

500

None

TRUE

FALSE

LDP must be enabled.

RSVP must be enabled.

An SDP must be configured on the far-end.

Service MTU must match.

SDP ID must match.

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.

1500

1514

1518

It depends on the access port MTU.

It depends on the network port MTU.

CE1

CE2

PE1

PE2

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.

"client1" routes will be tagged with communities "North" and "West".

"client1" routes will be tagged with community "West".

"client1" routes will be tagged with community "North".

"client1" routes will be rejected.

Option A

Option B

Option C

Option D

"65100"

"65100 65200''

"65200 65100"

"65100 65250 65200"

R5-R2-R4-R8

R5-R1-R3-R4-R8

R5-R1-R2-R4-R8

R5-R1-R3-R7-R8

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.

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.

The receiving PE checks the l-TAG in the l-SID to determine if there is a local l-VPLS on the node.

The receiving PE checks the l-SID in the l-TAG to determine if there is a local l-VPLS on the node.

The receiving PE checks the service label in the mpls header to determine if there is a local l-VPLS on the node.

The receiving PE checks the multicast B-DA to see if an l-SID has been mapped to the B-DA that matches a local l-VPLS on the node.

Update

Open

Notification

Keepalive

show router route-table

show router bgp routes

show router bgp routes hunt

show router bgp neighbor received-routes

64491 {64492 64493}

64491

64492 64493 64491

{64492 64493)64491

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

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

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

The customer carrier network can be a pure IP network.

A CSC VPRN is configured on the CSC-CE to forward data packets to the network provider.

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

"Blue-Only"

"Extranet-VPN-Blue"

"Blue-Green"

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.

9100 bytes

9104 bytes

9108 bytes

9118 bytes

Configuring iBGP sessions between PEs residing in different customer carrier sites,

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring a CSC VPRN on each CSC-PE with a SAP interface towards the attached CSC-CE.

Configuring an IES service on PEL

Control plane scaling.

Data plane scaling.

Network touches.

Route table reduction.

OAM tools.

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.

SDP id

Service ID

VC Label

Tunnel Label

Customer id

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.

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

oam mac-populate

oam mac-ping

oam mac-trace

oam svc-ping

oam cpe-ping

Option A

Option B

Option C

Option D

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.

Preventing unwanted NLRI from entering the AS.

Filtering NLRI based on AS Path or prefix-lists,

Modifying the local preference of route advertisements.

Setting MED values of route advertisements.

Option A

Option B

Option C

Option D

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.

100

200

300

None

802.1D2004

802.1D 1998

comp-dot1w

PVST

100

200

1

2

100

250

The IGP cost

None

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

PE-A will require a SAP id of "sap 1/1/1" and PE-B will require a SAP id of "sap 1/1/1".

PE-A will require a SAP id of "sap 1/1/1:0" and PE-B will require a SAP id of "sap 1/1/1:0".

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

The ability to offer Internet connectivity and a variety of services over a single CSC VPRN interface.

The ability to maintain its own backbone.

The ability to learn system addresses of network provider PEs.

There is no need to manage end-customer services.

target:65100:2 and target:65100:3

target:65100:1 and target:65100:2

target:65100:1 and target:65100:3

target:65100:1, target:65100:2 and target:65100:3

Open

Update

Route Refresh

Notification

64496 64497

64496

64497

64497 64497

The BGP session from PE to P is not operational

The BGP session between PEs is operational

The BGP session between PE and CE is not operational

The BGP session from PE to CE is operational

The BGP session between PEs is not operational

P devices participate in service provider core routing.

P devices are not required to be MPLS-enabled.

P devices must be aware of the VPRNs.

P devices must support MP-BGP.

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.

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

The As-Path is not present as it was removed with the s-override configuration command

The As-Path is not present as it was removed with the o-as-path configuration command

The As-Path is not present as a policy was configured to set it to the null value

The As-Path is not present as VPN-IPv4 routes do not propagate the IPv4 As-Path BGP attribute

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.

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

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.

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

PE1 advertises the Red VPN routes and a default route to PE3.

The Internet VRF on PE3 imports the Red VPN routes advertised by PE1.

PE1 imports all Internet routes and advertises them to CE1 via the Red VRF.

PE3 advertises a default route from its Internet VRF instead of advertising all Internet routes.

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.

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.

TRUE

FALSE

Configuring iBGP sessions between PEs residing in different customer carrier sites.

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring a CSC VPRN on each CSC-PE with a SAP interface towards the attached CSC-CE.

Configuring an IES service on PEL

A single routing protocol for exchanging routes with both the internal customer routers and with the PE

MP-BGP to exchange routes with the PE.

MPLS and a routing protocol for the exchange of labels and routes with the PE

MPLS for exchanging labels with other CE devices

A routing protocol for exchanging routes with the internal customer routers and a routing protocol for exchanging routes with the PE

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The service ID of the service to which the SAP belongs.

The dot1p bits in the frame header.

The packet's Ethertype.

Classification

Marking

Queuing

Congestion management

Scheduling

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

The NRLI

The AFI

The SAFI

The extended community

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps

Shaping does not add latency.

Shaping does not add jitter.

Shaping protects downstream nodes from traffic bursts.

Shaping requires less memory to buffer packets.

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.

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.

H-QoS capabilities must be enabled globally on the router

A scheduler-policy must be configured.

The queues in the SAP-ingress and SAP-egress policies do not require additional configuration attributes to make use of the hierarchical schedulers.

The network queue policy must be configured to make use of the scheduler-policy.

The scheduler-policy must be referenced in the SAP-ingress and SAP-egress policies.

The scheduler-policy must be applied on the service SAP.

MAC learning

SA filtering

Routing table population

Frame forwarding

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

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.

An IES SAP

A VPLS SAP

A network port

AVPRN SAP

An access port

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.