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

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.

Classification

Marking

Queuing

Congestion management

Scheduling

Interfaces, ports, SAPs

Ports, ports, MDAs

MDAs, MDAs, ports

Interfaces, interfaces. MDAs

MDAs, ports, interfaces

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.

TRUE

FALSE

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.

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.

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.

network

scheduling

slope

SAP-ingress

network-queue

TCP port numbers

LSP EXP

DSCP

Source and destination IP addresses

Dot1p priority

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.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

Service labels are assigned based used on label blocks.

BGP-AD, RADIUS and Management are used for auto-discovery.

Service labels are signaled using MP-BGP.

Hierarchical VPLS is loosely defined in the standards.

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.

1

2

3

4

5

8

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

It is a parent scheduler.

It is the top-level scheduler.

It can allocate up to 50 Mbps of bandwidth to scheduler "low" since the bandwidth is not used by another Tier 3 scheduler.

It is a child scheduler.

It can only have queues as children.

Operates in transparent mode.

Carries RSTP BPDUs only.

Assigns RSTP state to other VPLS services.

Allows load balancing among multiple management VPLS instances.

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.

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps

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.

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.

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

R1-R3-R8

R1-R2-R4-R8

R1-R3-R4-R8

R1-R2-R4-R3-R8

A single route for 192.168.0.0/16 is advertised.

BGP routes 192.168.1.0/27, 192.168.2.0/27, and 192.168.0.0/16 are advertised.

BGP routes 192.168.1.0/27 and 192.168.2.0/27 are advertised, and 192.168.0.0/16 appears as a "Blackhole" route in the route table only.

The given export policy is invalid.

Execute a command to re-evaluate all routes in the Local-RIB against the configured export policies.

Execute a command to re-evaluate all routes in the RIB-In against the configured import policies.

Execute a command to reset the BGP session with the affected peer or peers.

No further action is required.

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.

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.

Router B propagates the BGP update to routers D and C.

Router B propagates the BGP update to router D.

Router B detects duplicates in its BGP database and discards the update.

Router B propagates the update to routers A, C and D.

Router R3 rejects all updates originating in AS 65540.

Router R3 accepts updates received from router R1 and rejects updates transited through router R2.

Router R3 accepts updates transited through router R2 and rejects updates received from router R1.

Router R3 accepts updates from both routers R1 and R2.

BGP version number.

The local AS number.

The Hold Time.

Authentication.

Route-Refresh

OpenSent

Notification

Update

Keepalive

"65100"

"65100 65200''

"65200 65100"

"65100 65250 65200"

Option A

Option B

Option C

Option D

10.0.2.1

10.0.2.2

10.16.10.1

10.16.10.3

Option A

Option B

Option C

Option D

Update

Open

Notification

Keepalive

Option A

Option B

Option C

Option D

Routers R6, R1, R4 and R5.

Routers R1and R4.

Routers R1, R2, R3 and R4.

Routers R2 and R3.

Routers R1, R2, R3, R4 and R5.

Routers R1and R4 only.

Routers R1, R2, R3 and R4 only.

Routers R1, R4 and R5 only.

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.

Three primary paths,

Two primary paths and one backup path.

One primary path and two backup paths.

One primary path and one backup path.

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

The router ID of router A.

The router ID of router B.

The router ID of router C.

It will not be set.

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

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.

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.

A

B

C

D

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.

Reduced number of VPN tunnels that need to be managed

Centralized filtering policies with the introduction of a hub site

Optimal routing between all sites

Limited configuration required on the hub PE device

192.168.10.1

192.168.20.1

10.10.10.1

10.10.10.6

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.

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

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.

The protocol is configured under the config>service context

The protocol is configured under the global router context

The interface leading to the PE is defined as a protocol neighbor

The routing protocol used must be the same as the routing protocol used at other CE-PE locations in the same VPN.

A routing policy may or may not be required depending on the routing requirements and routing protocol

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.

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.

Dual CEs connected to redundant PEs can provide redundancy within a single site.

Site redundancy can be achieved by dual homing a single CE to one or more PEs.

Provider core LSPs can be LDP-based or RSVP-based.

The provider core maintains a full mesh of LSP tunnels and MP-BGP sessions between all P devices.

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

The customer carrier network can be a pure IP network.

The customer carrier provides Layer 2 and Layer 3 services to its end-customers.

A single CSC VPRN is configured on the network provider to support all services offered by the customer carrier.

In the case where the customer carrier offers VPRN services, the model is referred to as hierarchical VPRN.

Global, router

Router, router

Service, router

Router, service

Service, service

Router, global

Target:65100:2 and target:65100:3

Target:65100:1 and target:65100:2

Target:65100:1 and target:65100:3

Target:65100:1, target:65100:2 and target:65100:3

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.

Signaled via MP-BGP and used to identify the egress PE.

Signaled via T-LDP and used to identify the customer VPRN.

Signaled via MP-BGP and used to identify the customer VPRN.

Signaled via RSVP and LDP and used to identify the egress PE.

Signaled via RSVP and LDP and used to identify the customer VPRN.

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

The ASBRs exchange data packets that are encapsulated with a transport label and a service label.

The route target advertised in one AS is maintained and used in the remote AS.

The CLI command "configure router bgp enable-inter-as-vpn" is required on the ASBRs.

64491 {64492 64493}

64491

64492 64493 64491

{64492 64493)64491

Each PE must implement a policy to apply a unique SoO attribute to the set of routes received from each customer site.

A different BGP extended community is used on each PE that connects to a single site.

An import policy on the PE rejects a route if the attached SoO matches the configured value.

Import and export policies are applied on the PEs under the global BGP context.

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

PE2, PE3 and PE4

PE1, PE2, PE3 and PE4

This command is not required for the configuration of this PE hub and spoke VPRN.

It forwards the packet based on the label signaled by MP-BGP.

It decrements the TTL and forwards the packet based on the inner label.

It swaps the outer label then forwards the packet.

The P router does not perform any operations on labeled packets.

Option A

Option B

Option B

Option C

Option E

TRUE

FALSE

100

1

25

250

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.

SDP id

Service ID

VC Label

Tunnel Label

Customer id

Spanning tree must be enabled within the VPLS.

Spanning tree BPDUs must be untagged.

Spanning tree BPDUs must be tagged.

Spanning tree must be disabled within the VPLS.

MEP

MAP

MIP

MUP

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.

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

Event notification.

Loopback control.

Information.

Variable request.

Variable response.

802.1D2004

802.1D 1998

comp-dot1w

PVST

A management VPLS carries customer traffic over the non-blocking spoke-SDP

A VPLS service must be defined as a management VPLS upon creation to take on the role of a management VPLS

The state of a spoke-SDP within a user VPLS will take on the state of the spoke-sdp within the management VPLS.

The management VPLS must be created before the user VPLS.

Spanning tree will be disabled on the SAP that the PVST BPDU was received on.

The SAP that the PVST BPDU was received on will be disabled to prevent loops.

The spanning tree encapsulation will be dynamically changed to PVST on the SAP the PVST BPDU was received on.

The PVST BPDU will be ignored and 802.1D 2004 BPDUs will continue to be transmitted on the SAP.

Option A

Option B

Option C

Option D

5-one for each service.

2-one in each direction.

10-five in each direction.

None of the above.

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.

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.

H-VPLS

M-VPLS

PBB

MC-EP

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 frame will be forwarded out the port associated with the DA.

The frame will be discarded.

The frame will be flooded to all ports.

The frame will be fragmented and forwarded out the port associated with the DA.

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.

Bridge B

Bridge C

Bridge D

Bridge E

oam mac-populate

oam mac-ping

oam mac-trace

oam svc-ping

oam cpe-ping