Score Higher on Verified 300-540 | Designing and Implementing Cisco Service Provider Cloud Network Infrastructure (SPCNI v1.0) Exam Questions with Answers

R1 (AS 200) is multihomed to:

SP-1 in AS 300 via neighbor172.16.1.1

SP-2 in AS 400 via neighbor172.16.2.1

R1 must:

Advertiseonly locally originated prefixes(its own network 10.10.0.0/24).

NOTbecome atransit AS—i.e., R1 mustnotadvertise routes learned from one provider to the other.

The configuration includes AS-path access-lists:

ip as-path access-list 1 permit ^$

ip as-path access-list 200 permit ^200

ip as-path access-list 300 permit ^300

ip as-path access-list 400 permit ^400

^$ in AS-path ACL1matcheslocally originated routes(empty AS-path).

ACLs 200, 300, and 400 match routes whose first AS in the path is 200, 300, or 400 respectively (used if we needed to match those provider or customer routes).

To ensure each upstream provider only receiveslocally originatedroutes, we apply AS-path ACL1as anoutbound filter-liston each external BGP neighbor:

router bgp 200

neighbor 172.16.1.1 remote-as 300

neighbor 172.16.1.1 filter-list 1 out ? only advertise local prefixes to SP-1

neighbor 172.16.2.1 remote-as 400

neighbor 172.16.2.1 filter-list 1 out ? only advertise local prefixes to SP-2

This way:

Routes learned from SP-1 (AS 300) willnotbe advertised to SP-2 (AS 400) because their AS-path will begin with 300, not empty, so they fail ACL 1.

Similarly, routes from SP-2 will not be sent to SP-1.

Only R1’s own prefixes are exported, preventing AS 200 from becoming a transit network.

Comprehensive and Detailed Explanation From Exact Extract from my knowledge of Designing and Implementing Cisco Service Provider Cloud Network Infrastructure Outlines without Any External URL or Links:

Container orchestration is the automated management of container lifecycle tasks such as deployment, scaling, failover, and updates. In Cisco cloud and NFV design guidance, typical orchestration platforms includeDocker (with Swarm)andKubernetes, which integrate with Cisco networking and security for cloud-native workloads.

Dockerprovides the container runtime and can also perform basic orchestration through Docker Swarm mode, managing multi-container, multi-host deployments.

Kubernetesis a full-featured orchestration system that automates deployment, scaling, and operations of application containers across clusters. It is the de-facto standard used with Cisco Container Platform and other Cisco cloud solutions.

VMware vCenter, Cisco vManage, and Cisco vSmart focus on virtual machines or SD-WAN control, not container orchestration. Therefore, the correct tools areDocker and Kubernetes (A, D).

Cisco NSO-based orchestration principles in a multi-vendor environment require:

Service modeling using flexible, reusable YANG models

Abstraction of vendor-specific device differences

Transaction-safe configuration validation and execution

End-to-end automation across lifecycle stages (Day-0, Day-1, Day-N)

Scalability and adaptability for evolving requirements

Option C aligns perfectly with NSO service-modeling approaches:

Service models must be flexible, not rigid, enabling changes as technologies and needs evolve.

The architecture must support continuous refinement, enabling multi-vendor abstraction and lifecycle automation.

This ensures the network evolves seamlessly while remaining stable and automated.

Why the Other Options Are Incorrect

A – Simplified monitoring and post-deployment adjustments do not meet the core need for full lifecycle service modeling and abstraction.

B – Configuring devices individually contradicts the entire purpose of orchestration and abstraction.

D – A static YANG model cannot accommodate multi-vendor environments or future scalability.

Thus, only Option C matches full NSO-capable service modeling requirements.