4A0-C02 Nokia SRA Composite Exam Questions and Answers

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.

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.

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.

Three route targets and three route distinguishers

Five route targets and three route distinguishers

Three route targets and two route distinguishers

Five route targets and two route distinguishers

64491 {64492 64493}

64491

64492 64493 64491

{64492 64493)64491

Dotlp

EXP

DSCP

PREC

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.

Queue 5 is using priority mode.

UDP traffic can be serviced at a maximum rate of 20 Mbps.

Ping traffic is place in queue 5.

Queues 5 and 6 will receive equal portions of any remaining available bandwidth to meet their above-CIR bandwidth requirements.

Queue 3 is scheduled before queue 5.

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

A single-homed AS is also known as a stub AS.

A single-homed AS is also known as a leaf AS.

A single-homed AS uses either the ISP AS number or a private AS number.

A single-homed AS can be either transit or non-transit

The egress port scheduler takes the ratio of requested bandwidth to total bandwidth request from all children. It allocates bandwidth fairly, using these percentages and not exceeding the egress interface speed.

The egress port scheduler allocates bandwidth based on a WRR distribution method that takes into account the CIR and PIR requested at each level and the max speed, either default or configured, on egress.

The egress port scheduler allocates bandwidth on a first come, first served distribution method that takes into account the total CIR and PIR requested at each level and the max PIR requested from a single level.

The egress port scheduler will limit the bandwidth offered to the egress port based on the over-subscription factor, provisioned under the router interface, while using a WRR scheduler for the remaining bandwidth.

The egress port scheduler will use the Russian Dolls Method to allocate bandwidth to each level of requested bandwidth. HPO-Only is automatically set to 100%, allowing only high priority traffic to be buffered during congestion.

Router interfaces

Ingress MDA

Ingress Ethernet network ports

Egress Ethernet network ports

Service SAPs

network

scheduling

slope

SAP-ingress

network-queue

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

A point in the network where EXP bits can be mapped to one of eight predefined FCs, each one with its own queue.

A logical point in a service tunnel where all of customer traffic is aggregated.

A point at which the initial classification of customer traffic occurs.

A point in the network where QoS parameters are discarded in favor of lower-level hardware queuing functions, such as LLI (Link Layer Interleave).

A point in the network where traffic flows from multiple different services are queued together, based on forwarding class.

PIR

CIR

MBS

burst-limit

Queue 2 in "policer-output-queues," the default queue group used by policers on egress, because there are no queues in the "qg-10" queue-group template.

The local SAP's queue 1, because there is no queue in the "qg-10" queue-group template for EF traffic.

Queue 1 in the "qg-10" queue-group, because it exists by default and all traffic is mapped to it.

EF traffic is dropped because there are no queues in the "qg-10" queue-group template.

2

3

5

6

None of the above.

1,000 tokens

2,000 tokens

10,000 tokens

20,000 tokens

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.

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.

Level 8 within CIR.

Level 8 between CIR and PIR.

Level 8, once all PIR is serviced.

Level 1 within CIR.

Level 1 between CIR and PIR.

Level 1, once all PIR is serviced.

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.

Option A

Option B

Option C

Option D

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

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

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

All routes will appear in the RIB-Out.

100

The IGP cost

500

None

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.

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.

Access ingress, access egress, network egress

Access ingress, network ingress, network egress

Port ingress, port egress, shared bi-directional

Port ingress, port egress, network egress

Port ingress, network ingress, network egress

EXP markings on transit control traffic are not set correctly.

The priority of all self-generated traffic needs to be lowered to allow all other traffic to take precedence.

The priority of various control packets requires special treatment throughout the network.

The BGP process is consuming too many CPU cycles and is impacting OSPF performance.

None

2

3

4

packet filtering

prioritization of traffic flows

least cost routing

OAM functionality

separation between the data plane and the control plane

TRUE

FALSE

"65100"

"65100 65200''

"65200 65100"

"65100 65250 65200"

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.

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

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.

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

The prefix 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.

The prefix is located in Autonomous System 65100.

To utilize memory resources efficiently

To avoid Head of Line blocking

To achieve more granularity of QoS control

To make hierarchical scheduling/policing possible

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.

Router C sends the update to routers E and F only.

Router C sends the update to routers D, E and F.

Router C sends the update to routers A, B, E and F.

Router C sends the update to routers A, B, D, E and F.

Router R1forms an iBGP session with router R2, and an eBGP session with router R3.

Router R1forms iBGP sessions with routers R2 and R3.

Router R1forms eBGP sessions with routers R2 and R3.

The types of BGP sessions with routers R2 and R3 cannot be determined.

Origin, Next Hop and Local Preference.

Local preference, AS Path and Next Hop.

Aggregator, Next Hop and AS Path.

AS Path, Next Hop and Origin.

Two primary paths and one backup path.

One primary path and two backup paths.

Three primary path and one backup path,

Three primary paths.

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

100

The IGP cost

500

None

ecmp and multipath must be configured within the VPRN instance.

The RD of the VPRN on the local PE must be different from the RD of the remote PEs.

Is enabled in the config>router>bgp context

Allows a PE router to load share traffic across routes learned from both direct CE-PE peerings and MP-BGP peerings.

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

AS Path of 65100, Next Hop of router A.

MP-BGP for exchanging customer routes with other PEs.

A routing protocol for exchanging customer routes with the CE.

A label signaling protocol for defining transport tunnels between the PE and CE.

MPLS for exchanging labels with other provider core devices.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

It is a global network relying on interconnections provided by Internet service providers.

It is a continuous and interconnected set of public IP networks, advertised and shared across the globe.

It is a settlement-free global network that provides interconnection between Internet service providers.

It is a network that allows any Internet service provider to reach every other Internet service provider in the world.

The route with the lowest MED.

The route with the shortest AS Path.

The route received from the lowest peer IP address.

The route with the lowest Origin.

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.

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

The update is accepted and the route installed in the route table.

The update is accepted but the route will not be installed in the route table

The update is rejected

The peer session is dropped

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

A 32 bit IPv4 address followed by a 64 bit 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 FA 32 bit Route Target followed by a 32 bit IPv4 address

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

The ASBRs use MP-eBGP to peer with each other and exchange IPv4 routes between autonomous systems.

The ASBRs use MP-iBGP to peer with PE routers in their autonomous system and exchange VPN-IPv4 routes.

The ASBRs maintain a mapping of labels for IPv4 routes exchanged between autonomous systems.

The ASBRs require per-VPRN configuration.

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

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

TRUE

FALSE

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

VPLS 1 will be displayed as mVPLS and VPLS 100 will be displayed as VPLS.

VPLS 1 will be displayed as mVPLS and VPLS 100 will be displayed as uVPLS

VPLS 1 will be displayed as VPLS and VPLS 100 will be displayed as VPLS.

VPLS 1 will displayed VPLS and VPLS 100 will be displayed as uVPLS.

The time to relearn thousands of MAC addresses may result in excessive flooding or loss of packets.

If the FDB reaches the limit, the router will discard frames.

Discarding frames when the FDB limit is reached could deny SLA guarantees.

It could take several seconds to relearn thousands of MAC addresses denying QoS/SLA guarantees.

Monitor and troubleshoot a point-to-point full-duplex link.

Monitor and troubleshoot end-to-end services.

Can be used at the core to trigger MPLS protection mechanisms when a physical failure detection is not possible.

Should not be used at the core to trigger MPLS protection. BFD is the only method that can be used when physical failure detection is not possible.

Valuable in the last-mile connection to the Service Provider demarcation device.

MAC learned via SAP

MAC learned via SDP

There is not enough information to determine

Both will timeout at the same time

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.

Regular semantics will apply. It will be as if the SAP doesn't belong to a management VPLS.

All user VPLS SAPs will be disabled/pruned.

It is not possible to administratively disable a management VPLS.

Spanning tree will be automatically enabled on the user VPLS SAPs.

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

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

Traditional BGP loop detection mechanisms are unable to detect a loop in a VPRN scenario.

BGP loops are detected in a VPRN when the customer has separate sites using the same BGP autonomous system number.

The Alcatel-Lucent 7750 SR rejects routes containing AS_PATH loops by default.

When "remove-private" is configured at a PE, all routes received from the associated CE will have private AS numbers removed.

The VRF 10 on CSC-PE1 includes PE1 and PE2's system addresses.

The global routing table of PE1 includes PE2's system address.

The VRF 10 on CSC-PE2 includes CEI'S address.

The global routing table of PE2 includes CE1's address.

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.

Router R3 only.

Routers R3 and R4 only.

Routers R3, R4 and R5 only.

Router R2 does not advertise an update for the prefix.

Route reflectors propagate BGP learned routes to their clients.

Route reflectors require "n" iBGP sessions, where "n" is the number of BGP routers in the AS.

Route reflectors disable iBGP split horizon for all iBGP peers in the AS.

Route reflectors do not work in conjunction with confederations.

1

2

3

4

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.

This Bridge is furthest from the Root Bridge within the VPLS mesh.

This Bridge is the Root Bridge.

SAP 1/1/1 is an Edge Port.

This Bridge is closest to the Root Bridge within the VPLS mesh.

Set the bridge priority to 131071.

Set the bridge priority to 0.

Set the bridge priority to 32768.

Leave the bridge priority as the default.

If a spoke-SDP is configured between the new site and PE-D no further SDPs will be required.

If a mesh- SDP is configured between the new site and PE-D no further SDPs will be required.

A mesh- SDP must be configured between the new site and all other PEs within Metro B.

A spoke- SDP must be configured between the new site and all other PEs within Metro B.

100

1

25

250

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

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

VPLS is a bridged LAN service.

VPLS provides L2 VPN services to CEs.

VPLS is a point-to-point service where CEs are presented with point-to-point virtual circuits.

CEs that are members of the same VPLS service instance communicate with each other as if they are connected via a bridged LAN.

TLDP is used to create the inner label, RSVP is used to create the outer label.

TLDP is used to create the outer label, RSVP is used to create the inner label.

TLDP and RSVP cannot be used in the same network since they both provide the same label.

When RSVP is used, TLDP must be disabled and static vc labels should be used.

TLDP and RSVP can be used to create either labels based on how they are configured.

oam mac-ping

oam mac-populate

oamsvc-ping

oam mac-trace

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

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.