4A0-C02 Nokia SRA Composite Exam Questions and Answers

EF

H1

L1

H2

L2

8

16

6

4

3

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.

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

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.

VPLS switch identifier.

VPLS service identifier.

VPLS router identifier to all PEs.

A locally unique VPLS service identifier.

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.

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.

The policy should be placed in a "shutdown" state before changes are made.

A new network policy should be created and applied to the interface, overwriting the previous policy.

The policy must first be removed from the interface, then modified and re-applied to the interface.

Before the policy can be changed, it must be deleted with the no network qos command.

Before any changes are made to the policy, all network interfaces where the policy is applied have to be shut down.

TRUE

FALSE

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.

TRUE

FALSE

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

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

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

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

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

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

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

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

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

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

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

MAC learning

SA filtering

Routing table population

Frame forwarding

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 first 3 bits of the DSCP value are copied directly into the EXP field on the first network egress.

The EXP bits are set on the first network egress, based on a combination of the SAP-ingress classification and the network policy applied.

The 3 priority bits are copied directly from the dot1p header into the EXP field of the first MPLS header.

The EXP bits are set based on a default map that translates DSCP codes into internal forwarding classes on SAP-ingress.

Microflow reservations using RSVP

DSCP to EXP translation

Traffic classification

Automatic profiling and policy configuration

Buffer memory management

Traffic scheduling

64

8

3

16

1

oam vprn-ping source destination

oam vprn-ping source destination

vprn-ping router

Ping source

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

Show router bgp routes

Show router bgp routes prefix

Show router bgp routes self-originated

Show router bgp routes hunt

Show router bgp neighbor advertised-routes

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.

On the PE facing the CE neighbor

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

Static

RIP

OSPF

IS-IS

MP-BGP

BGP

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.

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.

Distributing the customer generated labels between sites

Distributing the customer routing information between

Forwarding the customer originated data packets to the appropriate destination

Forwarding the provider originated data packets to the appropriate customer site

Providing secure layer 3 routing exchange between sites

When sites of different VPRN customers use the same BGP AS number

When sites of the same VPRN customer use the same BGP AS number

When sites of different VPRN customers use different BGP AS numbers

When sites of the same VPRN customer use different BGP AS numbers

When the customer site AS number is the same as the provider AS number

MP-eBGP exchange of VPN-IPv4 routes between ASBRs residing in different autonomous systems.

MP-eBGP exchange of labeled IPv4 routes between route reflectors residing in different autonomous systems.

A VRF-to-VRF connection at the autonomous system border routers.

MP-eBGP exchange of VPN-IPv4 routes between PEs residing in different autonomous systems.

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.

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.

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

CE1

CE2

PE1

PE2

PE1

RR1

ASBR1

ASBR2

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

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

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

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

The Alcatel-Lucent 7750 SR allows the setting of the maximum number of routes that can be accepted in a VRF for a VPRN service.

The "maximum-routes" command is used to specify the maximum number of remote routes that can be held within a VRF for a VPRN service.

When the "maximum-routes" command is used with the "log-only" parameter, new routes are still learned.

Once the "threshold" value is reached, no new routes are added to the VRF.

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.

A full mesh VPRN

APE hub and spoke VPRN

An extranet VPRN

ACE hub and spoke VPRN

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.

A

B

C

D

Global, router

Router, router

Service, router

Router, service

Service, service

Router, global

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

Route-Refresh

OpenSent

Notification

Update

Keepalive

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.

ARIN

ICANN

RIPE NCC

LACNIC

APNIC

Router RA prefers the update received from router RR1.

Router RA prefers the update received from router RR2.

Router RA flags both updates as invalid.

Router RA accepts both updates and flags them as used.

The AS Path is set to 65540, and the Atomic Aggregate flag is set.

The AS Path is set to 65540 65550, and the Atomic Aggregate flag is set.

The AS Path is set to 65540 65550, and the Atomic Aggregate flag is not set.

The AS Path is set to 65550, and the Atomic Aggregate flag is not set.

100

The IGP cost

500

None

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.

Core and edge node failure recovery depends on IGP convergence.

Edge neighbor failure is detected by the eBGP session timeout.

BGP control plane convergence is independent of number of affected prefixes.

Upon BGP control plane convergence, an optimal path is installed in the FIB.

The aggregator attribute will not be present, and the atomic aggregate flag will not be set.

The aggregator attribute will not be present, and the atomic aggregate flag will be set.

The aggregator attribute will be present, and the atomic aggregate flag will not be set.

The aggregator attribute will be present, and the atomic aggregate flag will be set.

100

200

300

None

Well-known mandatory.

Well-known discretionary.

Optional transitive.

Optional non-transitive.

It is an optional transitive attribute.

It is an optional non-transitive attribute.

The atomic aggregate flag is always set if the aggregator attribute is set.

The atomic aggregate flag is always set if the AS Path information is lost due to aggregation.

100

250

The IGP cost

None

Option A

Option B

Option C

Option D

The BGP router that originates an update sets the Originator_ID.

The Originator_IDis set to the ClusterJD of the advertising router reflector.

Both confederation and route reflector topologies use the Originator_ID.

A BGP router ignores an update that contains its own BGP router ID as Originator_ID.

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.

Import policies affect ingress data flow.

Export policies affect ingress data flow.

Both import and export policies affect ingress data flow.

Policy direction and data flow are independent.

Only the BGP route is in the route table.

Both routes are in the route table.

None of the routes is in the route table.

Only the OSPF route is in the route table.

ISP 1 is downstream from ISP 3 and is expected to push more traffic toward ISP 3 than it pulls from it.

ISP 3 is downstream from ISP 1 and is expected to push more traffic toward ISP 1 than it pulls from it.

ISP 1 is downstream from ISP 3 and is expected to pull more traffic from ISP 3 than it pushes toward it.

ISP 3 is downstream from ISP1 and is expected to pull more traffic from ISP 1 than it pushes toward it.

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.

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.

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 router will accept the update and send a notification.

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

The router will accept the update and ignore the attribute.

The router will accept the update and propagate the attribute.

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

The overhead consists of 26 bytes. 14 DLC + 2 Ethertype + 8 for mpls labels + 2 for GRE

The overhead consists of 14 bytes for DLC.

The overhead consists of 18 bytes. 14 DLC +4 for mpls labels

The overhead consists of 22 bytes. 14 DLC + 8 for mpls labels

The mesh-sdp will be up.

The mesh-sdp will be down.

The mesh-sdp will only be up on PE-A.

The mesh-sdp will only be up on PE-C.

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.

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

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.

Discovery and auto-negotiation of OAM capabilities.

Link monitoring via event notifications.

Remote failure indication (RFI).

Remote Loopback

Latency and jitter across a service.

TRUE

FALSE

0

1

2

3

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.

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.

The same timer is used in all VPLS types.

Higher than the default timer of an I-VPLS.

Lower than the default timer of an l-VPLS.

The same timer as an l-VPLS.

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.

On initialization and then every hello-interval.

Only after receiving LACP packets.

Every 1 second.

Never.

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.

1500

1514

1518

It depends on the access port MTU.

It depends on the network port MTU.

MAC learning

SA filtering

Routing table population

Frame forwarding

The service MTU must be equal to or smaller than 1514 bytes.

The service MTU must be 1514 bytes.

The service MTU must be equal to or greater than 1514 bytes.

The service MTU can be any value.

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.

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.

MSTP

MCLAG

LACP

DHCP

A proprietary protocol

Unlike VPLS. VPWS appears as a multi-hop network to the customers.

Unlike VPLS, VPWS allows CEs that are member of the same service instance to communicate with each other as if they are connected via a bridged LAN.

Unlike VPWS, VPLS allows customers to view the network as a routed network.

Unlike VPWS, VPLS is a service where customer MAC addresses are learned.

This cannot be done.

Each VPLS will use the same pair of SDP's with the same endpoint configured with the option "load-balancing 2".

Each VPLS will need their own pair of spoke-SDP's configured. The spoke-sdp's that are to be active should be configured with the option "precedence primary".

Under the end-point configuration, enable load-balancing 2 and the MDU will load balance automatically.