Cisco 300-540 Dumps Questions Answers

In Cisco NFVI, themanagement noderelies 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 torestart 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 isB. docker.

The requirements in the scenario match the capabilities ofSegment Routing (SR-MPLS)combined withMPLS Performance Measurement (MPM):

1. Low-latency slice creation

Segment Routing allows deterministic paths using:

SR-TE (Traffic Engineering)

Colored or intent-based policies

Path selection based onlink latency, loss, bandwidth, or utilization

MPLS Performance Measurement supplies real-time data such as:

One-way delay

Round-trip delay

Loss metricsThis allows SR-TE to compute paths withminimum latency.

2. Secure slice with minimized transport cost

Segment Routing supports:

Slicing throughSR Policies

Steering encrypted traffic (IPsec/GETVPN) through specific SR tunnels

Traffic separation without requiring additional MPLS LSP state in the core

Optimizing transport cost via constraint-based TE computations

3. Transport SLA enforcement beyond best effort

SR-TE + MPM provides:

SLA-aware intent routing

Guaranteed performance paths

Automatic re-optimization if links violate latency or loss SLAs

Why the other options are incorrect

B. IPsec VPNProvides encryption but does not offerlatency-aware or SLA-based path selection. Not a slicing mechanism.

C. AWS Direct ConnectCloud connectivity service. Not related to MPLS performance monitoring or transport slicing.

D. Transit VPC for AWSUsed for SD-WAN cloud integration. Does not support SR-TE slicing or MPLS SLAs.

Therefore, onlySegment Routingprovides latency-based path computation, slicing, SLA guarantees, and cost optimization.

On R1 the configuration (simplified) is:

ip domain lookup

ip domain name ccnp.test

ip host www.ccnp.test 10.1.1.1 10.2.1.1 10.3.1.1

The ip host command statically maps the hostname www.ccnp.test

to three IP addresses. By default, Cisco IOS will always return these IP addresses to DNS queries in the same order they are configured (10.1.1.1, then 10.2.1.1, then 10.3.1.1). This means that clients will always attempt 10.1.1.1 first and will not achieve per-query load balancing across all three servers.

To enable DNS-based load balancing so that each successive query rotates the order of the addresses, Cisco IOS provides the command:

ip domain round-robin

This command enables round-robin rotation of multiple A records associated with a single hostname defined by ip host. With this feature enabled:

1st query: response order 10.1.1.1, 10.2.1.1, 10.3.1.1

2nd query: response order 10.2.1.1, 10.3.1.1, 10.1.1.1

3rd query: response order 10.3.1.1, 10.1.1.1, 10.2.1.1

Clients will typically try the first IP address in the list and use the others if the first one fails, exactly matching the requirement.

Why other options are incorrect:

A. ip domain retry 3 controls how many times the router retries DNS queries to a server; it does not control the order of multiple A records.

C. ip dns server turns the router into a DNS server but does not itself provide round-robin behavior for statically defined hosts.

D. maximum-paths 3 is a routing (IP forwarding) parameter for equal-cost multipath, unrelated to DNS resolution.