4A0-C02 Nokia SRA Composite Exam Questions and Answers

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 primary VRF on PE1 contains routes learned from spoke sites.

All traffic between spoke sites must pass through CE1.

The secondary VRF on PE1 is used to route data packets from the hub CE to the spoke sites.

PE1 advertises the primary VRF routes to CE1.

0 BGP and 2 MP-BGP sessions

2 BGP and 0 MP-BGP sessions

2 BGP and 1 MP-BGP sessions

2 BGP and 2 MP-BGP sessions

1 BGP and 2 MP-BGP sessions

Identify the egress PE in the MPLS domain

Signal the egress VPRN ID

Identify the ingress PE in the MPLS domain

Transport route updates between PEs

This command is required on all PE routers to distribute labeled IPv4 routes directly to PEs in remote AS.

This command is required on the ASBRs to exchange labeled IPv4 routes between the ASs.

This command is required on the route reflectors to exchange customer routes between ASs as labeled IPv4 routes.

This command is required on all PE routers to distribute labeled IPv4 routes to connected CEs.

Show service id base

Show router bgp routes

Show service id maximum-routes

Show router status

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

64496 64497

64496

64497

64497 64497

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

Three primary paths,

Two primary paths and one backup path.

One primary path and two backup paths.

One primary path and one backup path.

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.

Prefix list 192.168.0.0/16 through 18.

Prefix 192.168.0.0/17 longer.

Prefix list 192.168.0.0/17 through 18.

Prefix 192.160.0.0/13 longer.

All routers with which it has a BGP session.

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

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

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

Only eBGP neighbors.

Option A

Option B

Option C

Option D

Well-known mandatory.

Well-known discretionary.

Optional transitive.

Optional non-transitive.

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.

Option A

Option B

Option C

Option D

None

2

3

4

RIR assigned CIDR space.

External client address space.

Loopback or link addresses.

External link addresses.

All of the above.

65200 (65206 65202) 65100

(65206 65202)65100

65250 (65206 65202) 65100

65200 65100

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

65206 65202 65100

(65206 65202)65100

(65204 65206 65202) 65100

(65200) 65100

1

2

3

4

BGP version number.

The local AS number.

The Hold Time.

Authentication.

Option A

Option B

Option C

Option D

discard-unknown

mac-move

disable-learning

enable-mac-stability

TRUE

FALSE

TRUE

FALSE

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.

The CE must be configured with an MC-LAG to both PE devices.

The CE must be configured with LACP in active mode.

There is no configuration required on the CE.

The CE must be an Alcatel-Lucent 7750 SR.

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

0

1

2

3

A single management VPLS using RSTP can be used to block different SDPs for different VPLS services.

A single management VPLS using 802.1D-2004 can be used to block different SDPs for different VPLS services

There is no way to have load balancing across redundant spoke-SDPs.

Two management VPLS using RSTP can be used to block different SDPs for different VPLS services.

TRUE

FALSE

9100 bytes

9104 bytes

9108 bytes

9118 bytes

The switch with the highest bridge-id is selected as root.

The switch with the lowest bridge-id is selected as root.

The switch with the highest MAC address is selected as root

The switch with the lowest MAC address is selected as root.

TRUE

FALSE

TRUE

FALSE

Processing the TTL takes extra time.

MAC learning rate is doubled.

FDB size is doubled.

Requires a protocol to remove loops.

As frames leave the switch, the DA is populated into the FDB.

As frames enter the switch, the DA is populated into the FDB.

As frames leave the switch, the SA is populated into the FDB.

As frames enter the switch, the SA is populated into the FDB.

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.

The association must be defined in the user VPLS service.

The association is done when the user VPLS is associated with the same sdp-id in the management VPLS

The association is based on service IDs.

The association is based on customer IDs.

show stp 10

show service vpls 1 stp

C, show service id 10 stp

show service id 1 stp or show service id 2 stp

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.

The NRLI

The AFI

The SAFI

The extended community

oam mac-ping

oam mac-populate

oamsvc-ping

oam mac-trace

Marking/Remarking

Classification

Encapsulation

Scheduling

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.

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 DSCP value will be set to af21.

The DSCP value will be set to be.

TheDSCPvaluewillbesettoaf23.

The DSCP value will be set to af 12.

Thedot1pvaluewillbesetto5.

Thedot1pvaluewillbesetto2.

The dot1p value will be set to 3.

All out-of-profile traffic will be dropped before any in-profile is dropped.

The time average factor of 0 will discard all packets arriving in the shared buffer pool.

When the shared buffer utilization reaches 51%, in-profile packets might be dropped.

The highest probability with which an out-of-profile packet can be dropped is 20%.

When an in-profile packet arrives and the shared buffer utilization is at 69%, the packet will have approximately a 60% likelihood of being discarded.

TRUE

FALSE

packet filtering

prioritization of traffic flows

least cost routing

OAM functionality

separation between the data plane and the control plane

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

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

All TCP traffic will be mapped to forwarding class EF.

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

EF traffic will receive higher scheduling priority than H2 traffic.

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

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.

An SLA is used to provide automated, real-time testing and alarming for throughput, latency, and jitter across a provider's network.

An SLA is an agreement between a customer and a provider that dictates the treatment of customer traffic across the provider's network.

An SLA allows customers to control all traffic within the service provider's network by prioritizing their traffic over others as desired.

An SLA allows a customer to pre-mark traffic and ensure that traffic is treated as per the agreement within the provider's network.

An SLA is a standard set of network QoS policies that a provider shares to all its customers, allowing them to better understand the treatment of traffic within the provider's network.

A network LAG can only connect to another network LAG.

All port numbers must match between LAG endpoints.

All port physical speeds must match between members of a LAG.

It aggregates traffic from multiple physical ports into a single virtual port.

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

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.

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.

Interfaces, ports, SAPs

Ports, ports, MDAs

MDAs, MDAs, ports

Interfaces, interfaces. MDAs

MDAs, ports, interfaces

VPLS switch identifier.

VPLS service identifier.

VPLS router identifier to all PEs.

A locally unique VPLS service identifier.

Real-time

Assured

Non-conforming

High priority

In-profile

Set the CIR of queue 3 to a non-zero value corresponding to the customer's expected bandwidth requirements.

Set queue 3 to use priority mode.

Set the traffic classification of packets to in-profile.

Set the high-priority-only value to 0.

Map AF traffic to queue 1

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.

network

scheduling

slope

SAP-ingress

network-queue

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.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

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.

They are allocated to the RIRs by ICANN/IANA.

They are used when connecting ASs on the Internet.

They range from 1 to 56319.

They are assigned by the ISPs for enterprise networks.

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

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

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

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

7

13

21

42

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.

Add-Paths allows non-best paths to be advertised to a peer.

Add-Paths capabilities are exchanged between peers after the BGP session is established.

A BGP speaker must advertise the capability to receive multiple paths from its peer.

A BGP speaker must advertise the capability to send multiple paths to its peer.

Lower local preference is preferred over higher local preference.

Higher MED is preferred over lower MED.

Higher origin code is preferred over lower origin code.

Lower BGP router ID is preferred over higher BGP router ID.

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

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

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

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.

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

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

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

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

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

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

True

False

It is the customer responsibility to ensure their address space is unique

The Route Distinguisher ensures that addresses are unique between customers.

The Route Target ensures that addresses are unique between customers

The provider will advise the customers to change their addresses

The provider will use NAT to ensure that addresses are unique between customers

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

TRUE

FALSE

eBGP is used for route and label exchange between CSC-CE and CSC-PE routers.

iBGP can be used to distribute routes between CSC-CE and PE routers.

MP-iBGP is used to advertise routes between the CSC-PE routers.

MP-iBGP is used to advertise end-customer and Internet routes directly between the PE routers.

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

PE1 pushes a VPN label, a BGP label, and an LDP transport label on the IP packet.

CSC-CE1 pops the LDP label and swaps the BGP label.

CSC-PE1 pops the BGP label, swaps the VPN label, and pushes an LDP transport label.

CSC-PE2 pops the LDP and VPN labels and pushes a BGP label.

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.

Full mesh between all CE, PE and P devices

Full mesh between PE and P devices

Full mesh of P devices

Full mesh of PE devices

Full mesh between PE and CE devices

CSC does not allow a customer carrier to offer Layer 2 services to its end customers.

A CSC VPRN is configured on the network provider's CSC-PE routers.

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

The network provider provides an MPLS VPN backbone to the customer carrier.