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

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.

There can only be one community associated with a route.

Community is an optional non-transitive attribute.

Community is an optional transitive attribute.

Community is a well-known discretionary attribute.

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.

Option A

Option B

Option C

Option D

100

250

The IGP cost

None

The neighbor will send a Keepalive message.

The router is trying to initiate a TCP connection to that neighbor.

The router received an Open message with the correct parameters.

The router is actively exchanging updates with that neighbor.

Route-Refresh

OpenSent

Notification

Update

Keepalive

TTL is a well-known mandatory BGP attribute.

The default TTL value of an eBGP message is 1, and 64 for an iBGP message.

The default TTL value of an iBGP message can be modified using the multihop command.

The default TTL value of an eBGP message can be modified using the "ttl-security" command.

A single connection to a single service provider.

Two connections to a single service provider.

Two connections to two different service providers.

Multiple connections to different service providers.

config>router- confederation 65200 members 65202

config>router>bgp= confederation 65200 members 65202

config>router= confederation 65202 members 65200

config>router>bgp= confederation 65202 members 65200

Option A

Option B

Option C

Option D

AS Path of 65200, Next Hop of router A, Origin of IGP.

AS Path of 65200, Next Hop of router A, Origin of incomplete.

Null AS Path, Next Hop of router A, Origin of IGP.

Null AS Path, Next Hop of router A, Origin of incomplete.

Option A

Option B

Option C

Option D

The session between router A and router B.

The session between router C and router B.

The session between router D and router B.

Router B will learn the prefix over all of the sessions, then it will choose the best route.

RIR assigned CIDR space.

External client address space.

Loopback or link addresses.

External link addresses.

All of the above.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

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

65206 65202 65100

(65206 65202)65100

(65204 65206 65202) 65100

(65200) 65100

Option A

Option B

Option C

Option D

BGP Fast Reroute is triggered by IGP events.

The backup path is pre-computed and installed in the FIB.

BGP Fast Reroute is independent of number of affected prefixes.

BGP Fast Reroute uses the optimal path to the destination.

show router route-table

show router bgp routes

show router bgp routes hunt

show router bgp neighbor received-routes

Option A

Option B

Option C

Option D

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.

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.

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

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

MAC learning

Frame replication

Frame fragmentation

Frame forwarding

Must discard frames with an unknown destination MAC

MSTP

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.

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.

Discovery and auto-negotiation of OAM capabilities.

Link monitoring via event notifications.

Remote failure indication (RFI).

Remote Loopback

Latency and jitter across a service.

oam mac-populate

oam mac-ping

oam mac-trace

oam svc-ping

oam cpe-ping

I-VPLS is configured in the core of the network with an l-MAC address. This l-MAC address is the only MAC learned in the core

The B-VPLS and l-VPLS are configured in the edge. The B-VPLS is configured with a Backbone MAC and is the only MAC learned in the core

Each SDP is configured with a Backbone MAC to hide customer MAC addresses in the core

Each SAP is associated with a common l-MAC to hide customer MAC addresses in the core

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

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

9100

9104

9108

9122

9126

TRUE

FALSE

discard-unknown

mac-move

disable-learning

enable-mac-stability

PE-B will require a SAP id of "sap 1/1/1:500*".

PE-B will require a SAP id of "sap 1/1/1:100*".

PE-B will require a SAP id of "sap 1/1/1:500.200".

PE-B will require a SAP id of "sap 1/1/1:200*".

There will be no impact on the path-mtu.

The path-mtu will decrease by4 bytes.

The path-mtu will increase by 4 bytes.

The path-mtu will decrease by 8 bytes.

The path-mtu will increase by 8 bytes.

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.

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.

TRUE

FALSE

TRUE

FALSE

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.

Regular semantics will apply. It will be as if the SAP doesn't belong to a management VPLS.

All user VPLS SAPs will be disabled/pruned.

It is not possible to administratively disable a management VPLS.

Spanning tree will be automatically enabled on the user VPLS SAPs.

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

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

Global, router

Router, router

Service, router

Router, service

Service, service

Router, global

Identify the customer network on the egress PE

Establish the LSPs between PE devices

Identify the egress PE in the MPLS domain

Identify the customer network on the ingress PE

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.

This configuration is correct and complete.

This configuration is correct, but the interfaces must also be configured in the "configure router mpls" context.

There is no configuration required for LDP in the core network.

This configuration is correct but Targeted-LDP is also required.

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.

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

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

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

CE1

CE2

PE1

PE2

The neighbor shown is an ASBR router.

The address family between the peers should be VPN-IPv4 instead of IPv4.

The neighbor address cannot be the interface address 10.3.4.4.

The omitted AS number under "BGP summary" must be equal to 64496.

"Spoke.Sites" and "Hub_Site"

"Hub_Site"

"Spoke_Sites"

No communities should be imported

64496 64497

64496

64497

64497 64497

BGP sessions between RR1 and PE routers support only the IPv4 address family.

BGP sessions between RR2 and PE routers support only the VPN-IPv4 address family.

RR2 establishes BGP sessions with PEL PE2 and PE3.

RR1 establishes BGP sessions only with PE1 and PE2.

RSVP-TE has signaled a VPRN label.

RSVP-TE has signaled both VPRN and LSP labels.

MP-BGP has signaled both VPRN and LSP labels.

MP-BGP has signaled a VPRN label.

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.

Show router bgp routes

Show router bgp routes detail

Show router route-table

Show router route-table

Either (b) or (d)

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

show service id base

show router Idp bindings

show service id sdp detail

show service id vc-mtu

A P router may forward customer packets to their destination without the presence of a route to that destination

The ingress PE router may forward customer packets to their destination without the presence of a route to that destination

The egress PE router may forward customer packets to their destination without the presence of a route to that destination

Any provider core router (P or PE) may forward customer packets to their destination without the presence of a route to that destination

1

5

15

30

45

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

ASBR2 forwards the IP packet with one label to ASBR1.

ASBR1 forwards the IP packet with two labels to PEL

PE1 forwards an unlabeled IP packet to CE1.

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

Using dot1p bits of the 802.1q Ethernet frame header

Using DSCP bits within the ToS field of the IP packet header.

Using the IP precedence bits within the ToS field of the IP packet header.

Using the CLP bit of the ATM cell header.

Using the EXP bits of the MPLS transport label header.

3

64

72

16

56

The default forwarding class for all traffic, including ICMP, is BE, which is placed in queue 1.

The SAP has been shut down.

The IP-match criteria has been misconfigured for ICMP traffic.

Queue 3 has no rate or CIR configured and thus cannot hold any packets.

The SAP-ingress policy has not been applied to the SAP.

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.

The slope-policy

The SAP-ingress policy

The network-queue policy

The scheduler-policy

The network-policy

The WRED-policy

The arbitrator-policy

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.

The primary contributors to latency are distance, scheduling, and congestion.

The weighted round robin scheduling algorithm will result in more delay for high priority traffic than the regular round robin algorithm.

The round robin scheduling algorithm will result in less jitter for low priority traffic than a strict priority scheduler.

Packet loss can be reduced by decreasing the amount of buffer space available to a queue.

Latency can be reduced by increasing the amount of buffer space available to a queue.

TRUE

FALSE

Has the ability to distinguish traffic in 32 different ways.

Uses the RSVP protocol to create microflows through a network.

Has the ability to manually configure foiwarding classes through a network.

Uses the RSVP protocol to create macroflows through a network.

TRUE

FALSE

Native IP Packets will not be remarked.

Native IP Packets will be remarked.

Packets associated with a VPRN service on an upstream node will not be remarked.

Packets associated with an ES service on an upstream node will be remarked.

Real-time

Assured

Non-conforming

High priority

In-profile

8

3

4

5

6

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.

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

It will be discarded because the high-priority-only threshold is exceeded.

It will be queued but re-marked as "out-of-profile."

It will be queued in the reserved portion of the buffer pool and remain "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.

Operates in transparent mode.

Carries RSTP BPDUs only.

Assigns RSTP state to other VPLS services.

Allows load balancing among multiple management VPLS instances.

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.

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.

Set the CBS to 0.

Set the MBS equal to the CBS.

Set the high-priority-only equal to the MBS.

Set the MBS to 0.

Set the high-priority-only to 0.

Classification

Marking

Queuing

Congestion management

Scheduling

A standalone policer has no parent arbiter, while a CFHP pohlicer has a parent arbiter.

A standalone policer has a fixed PIR rate, while a CFHP poker's PIR rate can be dynamically adjusted by its parent arbiter.

Both standalone and CFHP policers use the FIR bucket to gain access to their fair share of the available bandwidth.

Both standalone and CFHP policers use a policer output queue to store packets before they are forwarded.

VPLS switch identifier.

VPLS service identifier.

VPLS router identifier to all PEs.

A locally unique VPLS service identifier.