Your Path to Success: How to Pass the Nokia 4A0-C02 Nokia SRA Composite Exam Exam

The As-Path is not present as it was removed with the s-override configuration command

The As-Path is not present as it was removed with the o-as-path configuration command

The As-Path is not present as a policy was configured to set it to the null value

The As-Path is not present as VPN-IPv4 routes do not propagate the IPv4 As-Path BGP attribute

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.

It is the most scalable of the Inter-AS models.

VRF configuration is not required on the ASBRs.

Most routers that support VPRN functionality do not support model A by default.

It is not necessary to run MPLS at the boundary between autonomous systems.

CE1

CE2

PE1

PE2

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 policy should be applied as an import policy on the PE connected to the main site of Customer 1.

The policy should be applied as an import policy on all the PEs connected to the sites of Customer 1.

The policy should be applied as an export policy on the PE connected to the main site of Customer 1.

The policy should be applied as an export policy on all the PEs connected to the sites of Customer 1.

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.

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

The solution scales as the number of end-customer routes increases.

There is no need to manage end-customer services.

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

The update is accepted and the route installed in the route table.

The update is accepted but the route will not be installed in the route table

The update is rejected

The peer session is dropped

One Route Distinguisher per VRF route

One Route Distinguisher per VRF

One Route Distinguisher per VRF per site

One Route Distinguisher per VPN

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

172.12.10.0/24, 172.12.20.0/24 and 172.0.0.0/16

172.12.0.0/16 only

172.12.10.0/24 and 172.12.20.0/24

172.0.0.0/16 only

The route with the lowest MED.

The route with the shortest AS Path.

The route received from the lowest peer IP address.

The route with the lowest Origin.

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

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000