Cisco 300-540 Exam Dumps

In a Cisco NFVI C-Series Pod, the Top-of-Rack (ToR) switches are almost always configured as a vPC pair. A vPC domain requires three mandatory components:

vPC domain ID

vPC peer-link

vPC peer-keepalive link ensures dual-active detection

In the exhibit:

The management interfaces are Tor-A Mgmt0: 10.10.10.1 and Tor-B Mgmt0: 10.10.10.2

These IPs are used commonly as the peer-keepalive endpoints

The physical uplinks to NFVI nodes form Port-Channel110

Since the configuration snippet already includes:

feature vpc

feature lacp

channel-group 110 mode active

The next required step in a Cisco NFVI + vPC configuration is to configure the peer-keepalive from ToR-A toward ToR-B:

vpc domain 1

peer-keepalive destination 10.10.10.2

This ensures:

vPC roles sync

Dual-active prevention

Stable operation for the NFVI C-Series rack

Why the Other Options Are Incorrect

A. vpc peer-link This is required but must be configured on the dedicated peer-link interfaces, not on the server-facing port-channel.

C. channel-group 110 mode on The correct mode is already configured: mode active for LACP. mode on disables LACP.

D. switchport mode access NFVI ToR links use trunking, not access mode, because servers carry multiple networks (control, compute, storage, management VLANs).

In Cisco NFVI, the management node relies heavily on Docker containers for:

NFVIS management functions

VIM services

Orchestration components

If the management node fails to start and the system shows:

docker.service: inactive (dead)

...then all Docker-based platform services also fail to start.

The correct recovery action is to restart the Docker engine:

systemctl restart docker

This brings up:

All NFVI-required Docker containers

Management services

REST APIs and cluster components

Why other answers are incorrect:

docker-kibana Only affects Kibana logging container

docker-cobbler Used for provisioning, not core NFVI management

kube-apiserver Part of Kubernetes cluster, but relies on Docker; restarting it won't help until Docker is running

Thus, the correct answer is B. docker.

Comprehensive and Detailed Explanation From Cisco NSO Orchestration Knowledge

In Cisco NSO deployments:

ncs-setup is only used once, during initial NSO instance creation.

ls -l nso-instance/packages/ simply lists packages --- not used to start NSO.

ncs -status checks status but does not run NSO.

To actually start the NSO service so that device packages (including ASAv service packages) can be loaded and orchestration can begin, the correct command is:

ncs

This launches the NSO runtime and loads all configured packages, enabling the SaaS ASAv service.

Comprehensive and Detailed Explanation

Cisco NFVIS logging levels (from lowest to highest):

critical

error

warning

info

debug highest verbosity

To capture maximum diagnostic detail, engineers must enable debug logging on the operational log type, which records system activity and runtime behavior.

Thus the correct command is:

system set-log logtype operational level debug

This provides the deepest troubleshooting visibility.

Comprehensive and Detailed Explanation From Cisco Cloud Architecture Knowledge

Event-driven applications require:

Stateless, micro-sized execution units

Automatic scaling

Code that runs only when triggered

No server or VM lifecycle management

This model is known as Function-as-a-Service (FaaS).

Cisco FaaS provides:

Serverless execution

Event-driven triggers

Deployment of atomic micro-functions

Automatic scaling and resource abstraction

Ideal environment for microservices and cloud-native workloads

Why the others are incorrect:

A . Cisco+ Hybrid Cloud for VDI delivers desktops, not serverless compute

C . Cisco+ Hybrid Cloud Virtualization VM-based infrastructure, not event-driven micro-functions

D . Cisco Intersight operational management tool, not a serverless execution platform