4A0-C02 Nokia SRA Composite Exam Questions and Answers

TRUE

FALSE

TCP port numbers

LSP EXP

DSCP

Source and destination IP addresses

Dot1p priority

TRUE

FALSE

Option A

Option B

Option C

Option D

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.

Real-time

Assured

Non-conforming

High priority

In-profile

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.

The three most significant (first) bits define 8 forwarding classes.

The three least significant (last) bits of the DSCP specify the drop probability.

The full 8 bits of the TOS field are used for DSCP.

To convert DSCP to IP precedence, the three most significant (first) bits are matched.

DSCP provides for eight drop probabilities.

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps

802.1p adds 16 bits to the Layer 2 header,

802.1p adds 16 bits to the Layer 3 header.

802.1p specifies 64 different priority levels.

802.1p uses a field in the 802.1Q header.

802.1p uses a field in the Layer 3 IP header

802.1p defines a 3-bit Class of Service field.

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

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.

H-VPLS

M-VPLS

PBB

MC-EP

802.1D2004

802.1D 1998

comp-dot1w

PVST

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.

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.

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

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.

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:*".

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

100

200

1

2

Spanning-tree BPDUs are returned to the sender.

The MEP sees its own CFM frames returned to itself.

This is not a function of IEEE 802.lag but of 802.1D

The record field of the CFM frame keeps track of chassis-mac addresses.

Theloopbackfuntionin802.1ag is an intrusive test that will stop customer data.

The loopback function of 802.lag is a non-intrusive "ping" sent from a MEP to a remote MEP or MIP.

The loopback function in 802.3ah is an intrusive test that will loop customer data.

The loopback function of 802.lag is an intrusive test that will "loop" all customer data back to the original sender.

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.

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.

Path-ID is a four-octet identifier pre-pended to the NLRI field of a BGP update.

Path-ID is an optional transitive attribute used to advertise multiple paths.

Path-ID uniquely identifies each path advertised to a neighbor.

A BGP speaker that re-advertises a route must generate its own Path-ID.

Advertising external networks into IGP.

Using system addresses for setting up iBGP sessions.

Exporting the networks associated with the external links of eBGP peers into BGP.

Optimizing BGP route table by exporting IGP routes into BGP.

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.

Option A

Option B

Option C

Option D

If no import policy is specified, all valid BGP routes are passed to the BGP route selection process.

If no export policy is specified, all non-BGP routes are populated into RIB-Out.

If no import policy is specified, all BGP routes are populated into the route table.

If no import policy is specified, only valid BGP routes are populated into RIB-Out.

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

"client2" routes will be tagged with communities "West", "North" and "South".

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

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

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.

70 seconds

25 seconds

20 seconds

30 seconds

140000 137000

137000 140000

23456 23456

200 140000 137000

Option A

Option B

Option C

Option D

Only entry 10 is executed for "client1" and "client2".

Entries 10 and 20 are executed for "client1", and entries 10 and 30 are executed for "client2".

Entries 10 and 20 are executed for "client1", and entries 10, 20 and 30 are executed for

"client2".

Entry 10 is executed for directly-connected routes, entry 20 for "client1" and entry 30 for "client2".

100

250

500

None

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.

show router route-table

show router bgp routes

show router bgp routes hunt

show router bgp neighbor received-routes

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.

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.

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.

sap 1/1/1

sap 1/1/1:0*

sap 1/1/1:0

sap 1/1/1:*

The individual SAPs and SDPs will age out MAC addresses for this VPLS.

Aging will be disabled for locally-learned MAC addresses for this VPLS.

Aging will be disabled for both local and remote MAC addresses for this VPLS.

Aging will be disabled for remote MAC addresses for this VPLS.

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.

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

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.

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.

Control plane scaling.

Data plane scaling.

Network touches.

Route table reduction.

OAM tools.

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.

64

8

3

16

1

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.

PIR

CIR

MBS

burst-limit

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

Option A

Option B

Option C

Option D

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.

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

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.

Option A

Option B

Option C

Option D

The session between AS 65202 and AS 65206 is an iBGP session.

The session between AS 65204 and AS 65206 is an intra-confederation eBGP session.

A BGP session is required between AS 65202 and AS 65204.

The BGP sessions within the member ASs are known as inter-confederation BGP sessions.

64496 64512

64512

64496

64512 64496

The route update sent from PE1.

The route update sent from PE2.

The route update sent from ASBR1.

The route update sent from ASBR2.

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

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

ASBR2 sends the IP packet with one label to ASBR1.

ASBR1 sends the IP packet with one label to PEL

PE1 pops one label off the IP packet and forwards it to CE1.

These routes will not appear on CE-B

Type 1 LSAs

Type 3 LSAs

Type 5 LSAs

Type 7 LSAs

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

All traffic exchanged between end-customers is carried over a single CSC VRF.

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

The customer carrier network can be a pure IP network.

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

A full mesh VPRN

APE hub and spoke VPRN

An extranet VPRN

ACE hub and spoke VPRN

The policy should be applied as an import policy on the PE connected to the main site of Customer 1.

The policy should be applied as an import policy on all the PEs connected to the sites of Customer 1.

The policy should be applied as an export policy on the PE connected to the main site of Customer 1.

The policy should be applied as an export policy on all the PEs connected to the sites of Customer 1.

BGP sessions established between RR2 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR1 and the PEs support the IPv4 address family only.

BGP sessions established between RR1 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR2 and the PEs support the IPv4 address family only.

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.

Traditional BGP loop detection mechanisms may detect a loop in the VPRN scenario, which in fact is not present.

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

When the CLI command "config>router>bgp# loop-detect discard-route" is used, the Alcatel-Lucent 7750 SR sends a notification to the remote peer and drops the BGP session.

In VPRN implementations where the CE-PE protocol is BGP, it is possible for separate sites of the same customer to use the same BGP autonomous system number.

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.

PE1

RR1

ASBR1

ASBR2

OSPF

ISIS

MP-BGP

BGP

Targeted LDP

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

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

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.

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

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

PE1 advertises spoke routes to CE1.

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

The secondary VRF on PE1 contains routes learned from the spoke sites.

Spoke sites do not learn routes from other spoke sites directly.

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 VRF per route

One label per VRF per next-hop

One label per VRF

All of the above

A and C

B and C

Model B does not require the configuration of VPRN instances on ASBRs.

The ASBRs peer with each other to transport VPN-IPv4 routes between autonomous systems.

PE routers distribute VPN-IPv4 routes to their local ASBR.

One single ASBR is required in each AS to hold the routes for all VPRNs.

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

MAC learning

SA filtering

Routing table population

Frame forwarding

Mesh-sdp

Spoke-sdp

MPLS

GRE

100

1

25

250

SDP id

Service ID

VC Label

Tunnel Label

Customer id

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.

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are not being dropped on ingress.

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are being dropped on ingress.

A commercial builder has requested numerous dot1Q epipes, VPRNs, and VPLS services to a business park and is only paying up to a maximum 200Mbps.

An equipment manufacturer has requested a NULL epipe service that will transparently pass dot1Q between the new location and national headquarters.