Nokia 4A0-C02 Nokia SRA Composite Exam Exam Practice Test

There are a maximum of 8 levels of priority serviced using a round-robin algorithm.

The default scheduler will spend an equal amount of time in each queue, as long as there is traffic present

The H1 internal forwarding class will receive its CIR before AF traffic.

Orphaned queues will be scheduled out of the BE queue.

A queue servicing EF and AF traffic will require explicit configuration to set the queue to expedited.

The scheduler will be allocated its "within CIR" bandwidth before all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at all levels have received their "within CIR" bandwidth.

The scheduler will not be allocated its "within CIR" bandwidth.

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.

DSCP is part of the Layer 3 header.

DSCP is a 6-bit field.

DSCP specifies eight different priorities.

DSCP specifies four precedence levels.

DSCP is part of the Layer 2 header

DSCP specifies 128 different per-hop behaviors.

To utilize memory resources efficiently

To avoid Head of Line blocking

To achieve more granularity of QoS control

To make hierarchical scheduling/policing possible

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.

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.

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.

packet filtering

prioritization of traffic flows

least cost routing

OAM functionality

separation between the data plane and the control plane

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.

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

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.

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.

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

An IES SAP

A VPLS SAP

A network port

AVPRN SAP

An access port

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

DSCP

PREC

Dot1p

ToS

Q-in-Q

All buffer space is initially allocated to access pools, and some of it is reallocated to network pools if network interfaces are configured on it.

All buffer space is initially allocated to network pools, and some of it is reallocated to access pools if service SAPs are configured on it.

Buffer space is allocated 50% for access pools and 50% for network pools.

Buffer space is allocated 25% for access pools and 75% for network pools.

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as "discard eligible."

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

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.

PIR = 4 Mbps, CIR = 1 Mbps

PIR = 1 Mbps, CIR = 1 Mbps

PIR = 10 Mbps, CIR = 1 Mbps

PIR = 5 Mbps, CIR = 5 Mbps

PIR = 1.25 Mbps, CIR = 1.25 Mbps

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.

Resources consumed at the sender and receiver PEs can be reduced by using BGP ORF.

BGP ORF allows a receiving PE to filter out unnecessary inbound routes.

A PE indicates its ORF capabilities to its neighbor PE in a BGP Open message.

BGP ORF is most effective when a large number of routes is being exchanged between two peers, and most routes are filtered out on arrival.

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

A data packet destined to a remote AS is encapsulated with three labels within the originating AS.

The ASBR redistributes VPN-IPv4 updates to its ASBR eBGP peers.

PE routers in different ASes exchange IPv4 routes directly between each other using eBGP.

The advertising ASBR assigns a new label to the route before sending it via an MP-eBGP update to its ASBR peer.

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

MP-BGP for exchanging customer routes with other PEs

A routing protocol for exchanging customer routes with the CE

MPLS for exchanging labels with other provider core devices

MPLS for exchanging labels with the CE devices

Targeted LDP for exchanging VPRN labels with other PE devices

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

Distributing customer routing information between sites

Forwarding customer data packets

Providing an integrated billing solution

Maintaining separation between distinct customer networks

Allowing the implementation of Layer 3 devices in the provider core

In the routing updates exchanged from CE to PE

In the routing updates exchanged from PE to PE

In the routing updates exchanged from P to PE

In customer packets as they traverse the provider core

In all route tables of the VPRN control plane

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.

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.

0

5

10

15

45

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.

CE2 forwards an unlabeled IP packet to PE2 via the VPRN interface.

PE2 pushes two labels on the IP packet and label-switches the packet to ASBR2.

ASBR2 pops one label from the IP packet and label-switches it to ASBR1.

ASBR1 pushes two labels on the IP packet and label-switches the packet to PEL.

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.

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.

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.

The ORF configuration must be done under the BGP neighbor context only.

When sending is enabled, the ORF function takes the route target list configured in all outbound policies and pushes this list to the peer by default.

When configuring ORF, the session with the peer must be cleared/reset for the new capability negotiation to take place.

When Outbound Route Filtering is configured, both the sending and acceptance of ORF are enabled by default.

1

2

3

4

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

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

1

5

15

30

45

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

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.

There is no effect. The MAC addresses for the l-VPLS age out independently of the aging of B-VPLS addresses.

The MAC addresses for the l-VPLS will age out immediately following the remote-age out of the backbone-macs of the B-VPLS.

By default, the remote-age timer of the B-VPLS is configured to 0 and addresses do not age out. The l-VPLS uses its own timer.

The same timer is used for B-VPLS and l-VPLS addresses on the node.

Isolates collision domains.

Requires layer 2 loop prevention.

Slow response to topology changes.

Limited to 4094 vlans per switch.

Increased flooding.

Event notification.

Loopback control.

Information.

Variable request.

Variable response.

The Alcatel-Lucent 7750 SR supports 1:1 mapping of I-VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports 1:1 andM:1 mapping of l-VPLS services to B- VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to l-VPLS services.

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.

sap 1/1/1

sap 1/1/1:0*

sap 1/1/1:0

sap 1/1/1:*

An error will be generated and the configuration will not be allowed.

The filter entry will be ignored and traffic matching the criteria will be forwarded

All traffic matching entry 20 will be dropped.

Traffic matching entry 20 will be forwarded to sdp 100: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

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

The 1-SID must be explicitly configured.

The 1-SID only supports a range from 1 to 255.

The 1-SID will default to 511 .the value of the service-id.

Thel"SIDwilldefaultto131582, the value of the service-id + 131071.

The port that the SAP belongs to must have the correct ether type configured.

The SAP must be configured with the right VLAN tag.

The SDP VC type must be configured as type VLAN and the correct vlan-vc-tag must be specified.

All of the above.

9000

1514

1000

100

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

5-one for each service.

2-one in each direction.

10-five in each direction.

None of the above.

Control plane scaling.

Data plane scaling.

Network touches.

Route table reduction.

OAM tools.

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.

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.

0

1

2

3

Loss of connectivity.

Unidirectional Loss.

Loop detection.

Merged Services.

End-to-end bit error rates.

oam mac-ping

oam mac-populate

oamsvc-ping

oam mac-trace

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

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.

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.

Option A

Option B

Option C

Option D

BGP version number.

The local AS number.

The Hold Time.

Authentication.

Configure router bgp shutdown

Clear router bgp neighbor soft

Clear router bgp neighbor soft-inbound

Clear router bgp protocol

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.

BGP is waiting for the TCP connection to be completed.

BGP has established a TCP connection, and an Open message has been sent to that neighbor.

The BGP session has been interrupted, and a TCP connection is being re-established.

BGP has failed to establish a TCP connection to that neighbor, and ConnectRetry has been reset to zero.

With the same method and attribute as 16-bit AS numbers.

With the same method as 16-bit AS numbers, but using the AS4_Aggregator attribute.

Aggregation is not yet supported with 32-bit AS numbers.

By using a dummy value of 23456 in the 16-bit AS aggregator field. This value lets the router know it needs to read the 32-bit AS number that is contained in the nextTLV.

RIR assigned CIDR space.

External client address space.

Loopback or link addresses.

External link addresses.

All of the above.

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.

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.

100

The IGP cost

500

None

1

2

3

4

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.

The first BGP route.

The second BGP route.

Both routes are used.

It is impossible to determine without the value of the origin code for both routes.

The routes from routers R1, R2 and R5.

The routes from routers R1and R2.

The routes from routers R2 and R5.

Two routes are chosen at random and advertised to router R4.

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.

AS Path of 65200, local-preference of 100.

AS Path of 65200, local-preference of None.

Null AS Path, local-preference of 100.

Null AS Path, local-preference of None.

140000 200 135000

137000 140000 200 135000

140000 23456 135000

135000 200 140000

Well-known mandatory.

Well-known discretionary.

Optional transitive.

Optional non-transitive.

To protect external networks from instability.

To communicate the architecture of an AS to external ASs.

To protect the local AS and other external ASs from bad NLRI.

To optimize ingress and egress traffic patterns to best serve the users of the AS.

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.

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.