4A0-C02 Nokia SRA Composite Exam Questions and Answers

DSCP value

802.1p value

IP DF bit

TCP/UDP port numbers

HTML version number

FC H1, high

FC EF, high

FC H2, low

FC EF, low

TRUE

FALSE

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.

Each network egress port receives its own buffer pool.

Each SAP-egress port receives its own buffer pool.

All SAP-ingress ports on the same MDA share a buffer pool.

All the network ingress ports on the same MDA share a buffer pool.

Each network ingress port on the same MDA receives its own buffer pool.

Queue 2 in "policer-output-queues," the default queue group used by policers on egress, because there are no queues in the "qg-10" queue-group template.

The local SAP's queue 1, because there is no queue in the "qg-10" queue-group template for EF traffic.

Queue 1 in the "qg-10" queue-group, because it exists by default and all traffic is mapped to it.

EF traffic is dropped because there are no queues in the "qg-10" queue-group template.

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.

To utilize memory resources efficiently

To avoid Head of Line blocking

To achieve more granularity of QoS control

To make hierarchical scheduling/policing possible

2

3

5

6

None of the above.

DSCP

PREC

Dot1p

ToS

Q-in-Q

BE

AF

EF

H1

TRUE

FALSE

AF

EF

H2

H1

BE

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.

Ensure that traffic flows conform to their traffic profile.

Log violations of metered traffic flows exceeding the CIR value set on the entity across which the traffic is moving.

Provide fairness between traffic flows, so that conforming (in-profile) traffic flows are not starved of bandwidth and/or buffer space by non-conforming (out-of-profile) flows.

Minimize packet loss and reduce end to end latency.

Ensure that variable latencies do not cluster short bursts of originally conforming packets and render them nonconforming.

af11

af12

af31

af33

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

TRUE

FALSE

The IOM3 adds more memory to both forwarding complexes which increases the total number of queues available.

The IOM3 only contains a single forwarding complex which reduces the number of queues used.

The IOM3 allows multiple forwarding classes to be assigned to a single queue.

The IOM3 allows queues to be dynamically allocated between ingress and egress.

The IOM3 has a larger CPU capable of tracking active hardware queue utilization and adjusting memory allocation accordingly.

140000 200 135000

137000 140000 200 135000

140000 23456 135000

135000 200 140000

10.0.2.1

10.0.2.2

10.16.10.1

10.16.10.3

1

2

3

4

100

The IGP cost

500

None

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.

1

2

3

None

Two routes from router R4.

Two routes from router R5.

Two routes; one from router R4 and one from router R5.

Four routes; two from router R4 and two from router R5.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

To ensure proper route propagation inside a transit AS.

To ensure that all routers are directly connected.

To ensure that all routers run iBGP inside a transit AS.

To maximize control plane scalability.

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

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

"client1" routes will be tagged with community "North".

"client1" routes will be rejected.

"client2" routes will be only tagged with communities 'East'' and "South".

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

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

"client2" routes will be rejected.

The routes are in the RIB-In.

The routes are in the Loc-RIB.

The routes are in the RIB-Out.

The routes are not in any of the BGP databases.

100

The IGP cost

500

None

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.

7

13

21

42

ISP 1 and ISP 2 have a public transit relationship, while ISP 3 and ISP 4 have a private transit relationship.

ISP 1 and ISP 2 have a private transit relationship, while ISP 3 and ISP 4 have a public transit relationship.

ISP 1 and ISP 2 have a private peering relationship, while ISP 3 and ISP 4 have a public peering relationship.

ISP 1 and ISP 2 have a public peering relationship, while ISP 3 and ISP 4 have a private peering relationship.

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.

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

Only the route reflector is configured with a cluster id.

There can only be one route reflector in a cluster.

Clients should have iBGP sessions with each other to maintain the mesh.

There can only be one level of route reflectors in the topology.

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.

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 router ID of router A.

The router ID of router B.

The router ID of router C.

It will not be set.

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.

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.

CE1

CE2

PE1

PE2

No need to build and maintain its own backbone.

The solution scales as the number of serviced customer carriers increases.

The solution scales as the number of VPNs offered by the customer carriers increases.

The ability to manage end-customer services.

It is an 8 byte value containing 3 fields

The Route Distinguisher must have the same value as the Route Target.

The Administrator field contains either an AS number or an IP number

To ensure uniqueness, Route Distinguishers are assigned by the IANA.

The Route Distinguisher is not used if the customer addresses do not overlap

The Assigned Number field must contain a public IP address

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

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.

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

The VRF 10 on CSC-PE1 includes PE1 and PE2's system addresses.

The global routing table of PE1 includes PE2's system address.

The VRF 10 on CSC-PE2 includes CEI'S address.

The global routing table of PE2 includes CE1's address.

1

5

15

30

45

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

End-customer routes are populated in the network provider CSC VRF.

The customer carrier does not learn any network provider internal routes.

The network provider learns customer carrier PE system addresses.

Routes exchanged between the customer carrier and the network provider are labeled.

"Extranet-VPN-Blue" and "Extranet-VPN-Green"

"Blue-Only"

"Extranet-VPN-Blue"

"Blue-Green"

A single routing protocol for exchanging routes with both the internal customer routers and with the PE

MP-BGP to exchange routes with the PE.

MPLS and a routing protocol for the exchange of labels and routes with the PE

MPLS for exchanging labels with other CE devices

A routing protocol for exchanging routes with the internal customer routers and a routing protocol for exchanging routes with the PE

TRUE

FALSE

ASBR1# show router 10 bgp routes vpn-ipv4

ASBR1# show router bgp routes

ASBR1# show router bgp routes vpn-ipv4

ASBR1# show router route-table

The lower the age-time, the greater the amount of flooding

The higher the age-time, the greater the amount of flooding.

The lower the age-time, the lower the amount of flooding.

There is no relationship between the age-time and the amount of flooding.

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

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

The vc-id is signaled in the control plane.

The vc-id is part of the data plane encapsulation.

There is a vc-id to vc-label mapping.

The vc-id has point to point significance.

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.

PE1

RR1

ASBR1

ASBR2

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.

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.

Spoke SDP

Mesh SDP

Either (a) or (b) will make this sentence true.

Neither (a) nor (b) will make this sentence true.

Filter Policies can only be applied on egress.

An IP filter can be applied on ingress at the same time a MAC filter is applied on the egress of the SAP.

Filter Policies can be based on IP, MAC, and VPI/VCI addresses.

Any number of ingress and egress filter policies can be associated with a SAP.

An IP filter and a MAC filter can be applied on the ingress SAP at the same time.

None of the above.

discard-unknown

mac-move

disable-learning

enable-mac-stability

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.

The PE devices participating in the VPLS mesh run a separate Spanning Tree instance in the Core. The Primary Bridge is the Root Bridge for the VPLS mesh.

The PE devices participating in the VPLS mesh determine which bridge is closest to Root Bridge. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge has the lowest bridge-id. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge is the Root Bridge. This becomes the Primary Bridge.

Processing the TTL takes extra time.

MAC learning rate is doubled.

FDB size is doubled.

Requires a protocol to remove loops.

SDP id

Service ID

VC Label

Tunnel Label

Customer id

TRUE

FALSE

The same as the number of alternate ports in the topology

1 per segment

The same as the number of root ports

1 per switch

oam mac-ping

oam mac-populate

oamsvc-ping

oam mac-trace

sap 1/1/1

sap 1/1/1:0*

sap 1/1/1:0

sap 1/1/1:*

TRUE

FALSE

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.

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.

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

Configure the local age timer to be larger.

Configure the local age timer to be lower.

Configure the remote age timer to be larger.

Configure the remote age to be lower.

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.

An additional management VPLS.

Another set of LSPs between PE1 and PE3 and between PE2 and PE4.

Another set of SDPs between PE1 and PE3 and between PE2 and PE4.

Load balancing has to be enabled within the management VPLS.

4094

8190

32768

131071

64491 {64492 64493}

64491

64492 64493 64491

{64492 64493)64491

The SDP path-MTU minus 14

The LMTU found in how router ldp bindings on the VPLS side of the spoke SDP

The configured service-mtu of the VPLS service

The LMTU found in how router ldp bindings on the VPLS side of the spoke SDP minus14

The SDP path-MTU

A full mesh VPRN

APE hub and spoke VPRN

An extranet VPRN

ACE hub and spoke VPRN

0 BGP and 2 MP-BGP sessions

2 BGP and 0 MP-BGP sessions

2 BGP and 1 MP-BGP sessions

2 BGP and 2 MP-BGP sessions

1 BGP and 2 MP-BGP sessions

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

CE1

PE2

PE1

CE2

The ability to offer Internet connectivity and a variety of services over a single CSC VPRN interface.

The ability to maintain its own backbone.

The ability to learn system addresses of network provider PEs.

There is no need to manage end-customer services.

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn