4A0-C02 Nokia SRA Composite Exam Questions and Answers

The MEP sees the CFM frame from a different MEG.

The MEP sees a different service-id in the frame sent by a MEP.

The MIP transmits the service-id for each service. The MIP should only see it ' s own service-id.

This is a function of 802,3ah EFM,

The overhead consists of 26 bytes. 14 DLC + 2 Ethertype + 8 for mpls labels + 2 for GRE

The overhead consists of 14 bytes for DLC.

The overhead consists of 18 bytes. 14 DLC +4 for mpls labels

The overhead consists of 22 bytes. 14 DLC + 8 for mpls labels

Number of LSPs.

Number of TLDP sessions.

Number of SDPs.

MAC address consumption in the FDB.

Bandwidth and replication requirements.

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.

TRUE

FALSE

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.

On initialization and then every hello-interval.

Only after receiving LACP packets.

Every 1 second.

Never.

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

If the MAC address of this new client device does not reach the upper limit of the configured total number of MAC addresses allowed in the VPLS forwarding database, then the new MAC address will be stored.

The new source MAC addresses will not be entered in the VPLS service forwarding database.

New local source MAC addresses will not be entered in the VPLS service forwarding database, but new remote MAC addresses would continue to be entered.

New remote source MAC addresses will not be entered in the VPLS services forwarding database, but new local MAC addresses would continue to be entered.

1500

1514

1518

It depends on the access port MTU.

It depends on the network port MTU.

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

Dot1Q

Null

Q-in-Q

Ipcp

BCP

Event notification.

Loopback control.

Information.

Variable request.

Variable response.

A Spanning Tree BPDU will be sent across the mesh flushing the FDB table in all devices participating in the VPLS instance.

Stale information will be used within the VPLS instance to forward traffic until the FDB ages out.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. Only MAC addresses associated with the PE that the failure occurred on will be flushed.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. The entire FDB in the VPLS instance will be flushed.

Learning should be disabled on both SAPs connected to the DPI device to prevent FDB instability

A MAC filter should be applied to both SAPs connected to the DPI to limit MAC learning on the port

An IP filter should be applied to both SAPs connected to the DPI to prevent FDB instability

The SAPs connected to the DPI should be configured with the " discard-unknown " feature to limit MAC learning on the port

sap 1/1/1:*.0 is a valid sap id.

sap 1/1/1:100* will accept frames with a single tag of 100.

sap 1/1/1:200* will strip the top tag of 200 and the bottom tag will be transparently passed.

sap 1/1/1:0* will accept all untagged frames.

sap 1/1/1:0* will accept any tagged frames.

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

0

1

2

3

The customer-id in this command is 9000.

The service-id in this command is 9000.

This value 9000 should be unique across the network as a best practice.

The vc-id will be 6 for the service by default.

The egress vc-label will be 9000.

Adding or removing a node may require several network touches.

Adding or removing a SAP may require several network touches.

Adding or removing a service may require several network touches.

Adding or removing an Epipe may require several network touches.

Provisioning is a factor for all Ethernet services.

This cannot be done.

Each VPLS will use the same pair of SDP ' s with the same endpoint configured with the option " load-balancing 2 " .

Each VPLS will need their own pair of spoke-SDP ' s configured. The spoke-sdp ' s that are to be active should be configured with the option " precedence primary " .

Under the end-point configuration, enable load-balancing 2 and the MDU will load balance automatically.

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.

VPLS1500 is a user VPLS.

VPLS 1500 is management VPLS.

Spanning tree BPDUs for the management VPLS are tagged.

Spanning tree BPDUs for the management VPLS are untagged.

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.

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

100

1

25

250

TRUE

FALSE

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.

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.

show stp 10

show service vpls 1 stp

C, show service id 10 stp

show service id 1 stp or show service id 2 stp

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.

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.

The LDP identifier

The Service identifier

The Route Target

The Route Distinguisher

The tunnel label

Option A

Option B

Option C

Option D

The route is ignored.

The route is flagged as invalid and placed in the LOC-RIB.

The route is flagged as invalid and placed in the RIB-In.

The route is flagged as invalid and placed in the RIB-Out.

Two primary paths and one backup path.

One primary path and two backup paths.

Three primary path and one backup path,

Three primary paths.

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.

Routers R6, R1, R4 and R5.

Routers R1and R4.

Routers R1, R2, R3 and R4.

Routers R2 and R3.

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

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.

Show router bgp routes

Show router route-table summary

Show router bgp routes vpn-ipv4 detail

Show router route-table

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.

It will label switch the packet based on this label

It will decrement the TTL and label switch the packet based on this label

It will SWAP the label for a new label and then label switch the packet

The P router does not perform any operation on this label

iBGP

eBGP

MP-iBGP

MP-eBGP

To limit the number of routes advertised from a customer site

To limit the number of routes learned from other customer sites CTo limit the size of the VRF table

To limit connectivity to selected customer networks

To perform packet filtering

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.

" Blue-Only "

" Blue-Only " and " Blue-Green "

" Green-Only "

" Extranet-VPN-Green "

" Blue-Green "

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 route learned from an eBGP peer.

The route with the lowest Origin.

The route with the lowest originator ID or BGP Identifier.

The route with the shortest AS path.

2

3

5

6

None of the above.

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.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

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.

1

2

3

4

5

8

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

The Route Target is added to an IPv4 route to create the VPN-IPv4 route.

The Route Target is an extended community string that identifies VPN membership.

A route can have only one Route Target.

The Route Target is a 64-bit value added to customer prefixes to make them unique.

The l-TAG in the l-SID is inspected to determine where the frame should be delivered.

When the B-MAC header is stripped the customer MAC address is then looked up in the FDB

The l-SID in the l-TAG is inspected to determine where the frame should be delivered.

The PE inspects the service label in the MPLS header before stripping the B-MAC header.

RSVP-TE

SP-VLAN

QinQ

Dot1Q

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.

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

Bridge B

Bridge C

Bridge D

Bridge E

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 local system has received a Keepalive message and is ready to exchange updates.

The local system is exchanging Update messages with its neighbor.

The local system has sent a Keepalive message to its neighbor and is waiting to receive one back.

The local system has sent an Open message to its neighbor and is waiting to receive one back.

1

32

64

255

OpenSent

Keepalive

Open

Notification

Update

" 65100 "

" 65100 65200 ' '

" 65200 65100 "

" 65100 65250 65200 "

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.

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.

" Spoke.Sites " and " Hub_Site "

" Hub_Site "

" Spoke_Sites "

No communities should be imported

eBGP peers typically use system addresses for session establishment.

eBGP peers are managed under a single administration.

eBGP peers do not propagate updates learned via iBGP.

eBGP peers are usually directly connected to each other.

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

Router R2 only.

Routers R2 and R3 only.

Routers R2, R3 and R4 only.

Routers R2, R3, R4and R5.

Policy changes are delayed until the peer router with the affected routes reboots.

Policy changes are delayed until route updates for affected BGP routes are received from peers.

Policy changes are delayed until BGP sessions are cleared or BGP is reset.

Policy changes are delayed until the router reboots.

Option A

Option B

Option C

Option D

In order to mark Layer 2 traffic, sgt-qos will set various ToS bits.

DSCP bits can be set per application, per routing instance.

The DSCP marking stays nc1 for all applications. Only the internal FC is manipulated across different applications.

In order to mark Layer 2 self-generated traffic, network interfaces must be set to dot1Q.

The internal forwarding class for self-generated traffic is set once and applied to the base router and all VPRN instances.

1536

1514

14%

1492

1488

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.

8

3

4

5

6

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.

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

It is the customer responsibility to ensure their address space is unique

The Route Distinguisher ensures that addresses are unique between customers.

The Route Target ensures that addresses are unique between customers

The provider will advise the customers to change their addresses

The provider will use NAT to ensure that addresses are unique between customers

Show service all

Show service id < service-id > detail

Show service id < service-id > base

Show service id < service-id > bindings

Show service sap-using

CSC eliminates the need for customer carriers to build and maintain their own MPLS backbone.

CSC is also known as carrier ' s carrier or carrier serving carrier.

The customer carrier provides VPN or Internet services to its end-customers.

A CSC VPRN is configured on the customer carrier ' s CSC-CE routers.

1

3

5

7

10

One VPRN, one route distinguisher, and two route targets

Two VPRNs, one route distinguisher, and three route targets

Two VPRNs, two route distinguishers, and three route targets

One VPRN, two route distinguishers, and three route targets

For the switches that are non-root or designated switches, the port with the highest combined cost to the root is the root port.

In the case where two switches have the same priority, the switch with the lowest MAC address becomes the root.

The switch port that is the greatest distance from the LAN to the root is the designated port.

All of the above.

On the PE facing the CE neighbor

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

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

Full mesh of MP-BGP between all P devices

Full mesh of MP-BGP between PE devices

Route reflector configuration between PE devices

Confederation configuration between PE devices

64496 64512

64512

64496

64512 64496

Relearning of the MAC address that was purged can only be done once customer traffic resumes.

Relearning of the MAC address that was purged can only be done with the " oam mac-populate " command.

Customer traffic destined to the MAC address that was purged will be dropped until the MAC address is relearned with the " oam mac-populate " command.

Relearning of the MAC address that was purged can only be done with the " oam mac-register " command.

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 mesh-sdp will be up.

The mesh-sdp will be down.

The mesh-sdp will only be up on PE-A.

The mesh-sdp will only be up on PE-C.

RSTP

Dynamic-cost

LACP active

Nothing, There are no loops in LAGs

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.

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

VPLS 100 was not actually configured as a management VPLS.

VPLS 10 and VPLS 20 are not actually configured as a user VPLS.

VPLS 10 and VPLS 20 are not using the same spoke-sdps that the management VPLS is using.

Based on the output there is now way of telling if there is a problem with the configuration.

MEP

MAP

MIP

MUP

MEP

MAP

MIP

MUP

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.

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.

Either a hub and spoke or an extranet VPRN

An extranet VPRN

A hub and spoke VPRN

Either a full mesh or a hub and spoke VPRN

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.

By using the MED attribute to carry the OSPF metric.

By defining Extended Communities for use as the Route Target

By using the Cluster List attribute to carry the network prefix

By defining support for the VPN-IPv4 address family

By adding an additional field to the BGP Update to carry the VPRN label

The VPRN ID must be the same value as is used in the vrf-target command

The VPRN ID must be the same value as is used in the route-distinguisher command

The router-id command should not be used in this context

The vrf-target command is mandatory

There is nothing wrong with this configuration

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn

Participate in service provider core routing

P devices are not required to be MPLS enabled. MPLS is only required on the PE devices

Run a common routing protocol with the CE router

Must support MP-BGP

Do not have any connections to the CE

Must be aware of the VPRNs

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

CE1

PE2

PE1

CE2

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.

Creating an export policy on CSC-CE1 and CSC-CE2 to advertise local PE addresses to the network provider.

Configuring eBGP between CSC-CE and CSC-PE routers; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring iBGP between PE and CSC-CE within each customer carrier site; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring MP-iBGP between PE1 and PE2; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

PE1 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

ASBR1 sends the data packet with one label: the BGP label.

ASBR1 sends the data packet with one label: the service label.

ASBR2 sends the data packet with three labels: the bottom label is a service label, the middle label is a BGP label, and the top label is an LDP label.

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.

A

B

C

D

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.

192.60.100.0

10.10.10.6

10.10.10.3

192.50.1.1

Traditional BGP loop detection mechanisms are unable to detect a loop in a VPRN scenario.

BGP loops are detected in a VPRN when the customer has separate sites using the same BGP autonomous system number.

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

When " remove-private " is configured at a PE, all routes received from the associated CE will have private AS numbers removed.

Show service 3

Show service id 3

Show service 3 base

Show service id 3 base

Show service 3 detail

Show service id 3 detail

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.

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring labeled iBGP sessions between PEs residing in different customer carrier sites.

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

Full mesh between all CE, PE and P devices

Full mesh between PE and P devices

Full mesh of P devices

Full mesh of PE devices

Full mesh between PE and CE devices

Real-time

Assured

Non-conforming

High priority

In-profile

Dotlp

EXP

DSCP

PREC

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.

BE

AF

EF

H1

All out-of-profile traffic will be dropped before that of any in-profile traffic.

The discard probability slope of an in-profile traffic is steeper than that of an out-of-profile traffic.

When the shared buffer utilization reaches 55%, both in-profile and out-of-profile packets may be dropped.

The maximum probability with which an out-of-profile packet can be dropped is higher than that of an in-profile packet.

When the shared buffer utilization is at 61%, only in-profile packets are currently in the shared buffer pool.

The connection between PE-A and PE-C

The connection between PE-A and PE-B

The connection between PE-D and PE-C

The connection between PE*D and PE-B

The slope-policy

The SAP-ingress policy

The network-queue policy

The scheduler-policy

The network-policy

The WRED-policy

The arbitrator-policy

H2

NC

L2

EF

H1

BE

The first 3 bits of the DSCP value are copied directly into the EXP field on the first network egress.

The EXP bits are set on the first network egress, based on a combination of the SAP-ingress classification and the network policy applied.

The 3 priority bits are copied directly from the dot1p header into the EXP field of the first MPLS header.

The EXP bits are set based on a default map that translates DSCP codes into internal forwarding classes on SAP-ingress.

Classification

Marking

Queuing

Congestion management

Scheduling

1,000 tokens

2,000 tokens

10,000 tokens

20,000 tokens

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

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.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

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.

Set the CIR of queue 3 to a non-zero value corresponding to the customer ' s expected bandwidth requirements.

Set queue 3 to use priority mode.

Set the traffic classification of packets to in-profile.

Set the high-priority-only value to 0.

Map AF traffic to queue 1

TRUE

FALSE

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.

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

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.

A device that provides no differentiation between customer traffic flows.

A device that classifies and marks customer traffic.

A device that uses MPLS EXP bits to differentiate between traffic flows.

A device that creates macroflows towards the core from multiple customer sites.

A device that passes macroflows while optionally changing QoS markings.

The NRLI

The AFI

The SAFI

The extended community

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

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

64

8

3

16

1

VPLS switch identifier.

VPLS service identifier.

VPLS router identifier to all PEs.

A locally unique VPLS service identifier.

On all ports on the Alcatel-Lucent 7750 SR.

At the junction of high-speed to low-speed links or at places of traffic aggregation.

At the junction of low-speed to high-speed links or at places of traffic aggregation.

On low-speed WAN links.

Nowhere. Shaping is only performed in hardware and serviced in a round-robin.

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.

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.

The EXP bits in the MPLS header.

The packet ' s source and destination IP addresses.

The packet ' s DSCP bits.

The dot1p bits in the frame header.

The ID of an SDP that is transporting the packet.

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.

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.

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.

EF

H1

L1

H2

L2

AF

EF

H2

H1

BE

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.

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.

None

2

3

4

64496 – 64511

1 – 56319

64512-65534

64513-65535

There are no defined private AS numbers; there are only private IP addresses.

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.

" .+ 65100 "

" 65100.+ "

" .* 65100.* "

" 65100 "

Route reflectors propagate BGP learned routes to their clients.

Route reflectors require " n " iBGP sessions, where " n " is the number of BGP routers in the AS.

Route reflectors disable iBGP split horizon for all iBGP peers in the AS.

Route reflectors do not work in conjunction with confederations.

Core and edge node failure recovery depends on IGP convergence.

Edge neighbor failure is detected by the eBGP session timeout.

BGP control plane convergence is independent of number of affected prefixes.

Upon BGP control plane convergence, an optimal path is installed in the FIB.

The entire confederation is viewed as a single AS by an eBGP peer.

Within a confederation, each member AS is considered as a stand-alone AS.

Member ASs within a confederation can use route reflection.

Member ASs must be fully meshed within a confederation.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

70 seconds

25 seconds

20 seconds

30 seconds

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.

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.

A route received from a BGP peer within the same AS.

A route originated by a router in a different cluster of the same AS.

A route received from a BGP peer from a different member AS of a confederation.

A route received from a BGP peer from the same member AS of a confederation.

It modifies the BGP advertisement logic.

It improves convergence times and allows for better load sharing.

It allows a router to advertise multiple external paths for a single prefix.

It supports both IPv4 and IPv6.

Router R1forms an iBGP session with router R2, and an eBGP session with router R3.

Router R1forms iBGP sessions with routers R2 and R3.

Router R1forms eBGP sessions with routers R2 and R3.

The types of BGP sessions with routers R2 and R3 cannot be determined.

Client1, Client2 and the aggregate.

Only the aggregate.

Only Client1 and the aggregate.

Only Client2 and the aggregate.

1

2

3

None

They provide both peering and transit services.

They provide services only to Tier 1 service providers.

They can be either public or private.

They provide services at the local, regional and continental levels.

Option A

Option B

Option C

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

Configure router bgp shutdown

Clear router bgp neighbor < ip-address > soft

Clear router bgp neighbor < ip-address > soft-inbound

Clear router bgp protocol

show router route-table

show router bgp routes

show router bgp routes < prefix > hunt

show router bgp neighbor < ip-address > received-routes

An import policy that rejects updates with an AS Path matching the regular expression " .+ 65540 .+ " .

An import policy that rejects updates with an AS Path matching the regular expression " .+ 65540 " .

An import policy that rejects updates with an AS Path matching the regular expression " 65540 .+ " .

An import policy that rejects updates with an AS Path matching the regular expression " 65540 " .

Option A

Option B

Option C

Option D

MPLS tunnels are used to carry transit traffic across the network.

A full mesh of iBGP peering sessions is not required,

Edge and transit routers need to be configured with BGP.

The transit routers need to support LDP or RSVP-TE LSPs.

100

The IGP cost

500

None

Option A

Option B

Option C

Option D

R1-R3-R8

R1-R2-R4-R8

R1-R3-R4-R8

R1-R2-R4-R3-R8