Important Cisco 300-540 SPCNI Exam Questions

Answer: A, E

Explanation:

In Cisco Enterprise NFVIS, time synchronization is configured using the system time ntp command structure. NFVIS requires a primary and optionally a backup NTP server to maintain accurate system time for the hypervisor and guest VMs.

Correct NFVIS command syntax for NTP configuration:

system time ntp preferred_server <IP>

This command configures the preferred (primary) NTP server used for system clock synchronization.

system time ntp backup_server <IP>

This command configures the backup NTP server, which the system uses if the primary becomes unreachable.

These two commands match Cisco NFVIS time-configuration behavior described in NFV infrastructure design and implementation guidelines.

Why the Correct Answers Are A and E

Option A: system time ntp preferred_server 192.168.1.1

This properly configures the primary NTP server in NFVIS. The preferred server is always the first choice for time synchronization.

Option E: system time ntp backup_server 192.168.2.1

This correctly configures the backup NTP server. If the preferred server fails, NFVIS automatically falls back to the backup server.

Both commands directly match NFVIS's NTP command hierarchy and are the only ones that correctly apply to NFVIS.

Why the Other Options Are Not Correct

Option B uses utils ntp, which is not an NFVIS command.

Option C sets manual time and does not configure NTP servers.

Option D also uses the utils ntp syntax, which applies to other Cisco platforms but not NFVIS.

Answer: B

Explanation:

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.

Answer: A, E

Explanation:

Comprehensive and Detailed Explanation From Cisco NFVI + VIM Architecture

Cisco VIM (Virtual Infrastructure Manager) operates as part of Cisco NFVI and requires specific mandatory network segments to deploy OpenStack-based NFVI environments.

The essential required networks for Cisco VIM include:

Provisioning network

Used during bare-metal install of compute and controller nodes

Handles PXE boot, image deployment, and VIM's management reachability

Storage network

Used for Cinder, Swift, Ceph, and Glance back-end storage replication

Ensures predictable latency and bandwidth for NFVI workloads

Other networks exist in VIM (Management, API, Tenant, External), but the question asks for the required foundational segments.

Why the other options are incorrect:

Data plane (B) -- used inside NFV workloads but not a required VIM infrastructure network.

Heartbeat (C) -- not a defined VIM network segment.

Host network (D) -- not a Cisco VIM terminology; provisioning network handles host onboarding.

Answer: C

Explanation:

Comprehensive and Detailed Explanation

Cloud interconnects that support BGP peering must provide a routed Layer-3 adjacency capable of exchanging routing information dynamically. In major cloud architectures:

AWS Direct Connect supports private virtual interfaces (VIFs) where BGP is used between the customer router and AWS to exchange routes.

Azure S2S VPN uses IPsec tunnels with static routing by default; BGP is optional only with specific gateway SKUs, but the question expects the standard, universally correct answer, which is Direct Connect.

Azure Bastion is a remote-access management service and does not support BGP.

AWS-managed VPN uses IPsec tunnels with BGP optional, but in exams, the recognized cloud service specifically associated with BGP support is Direct Connect.

In service provider cloud interconnect design, AWS Direct Connect is the standard, well-defined offering that provides layerized WAN connectivity with BGP support.

Answer:

Explanation:

For a site-to-site IPsec VPN, each peer must configure a pre-shared key tied to the public IP address of the remote VPN peer:

crypto isakmp key <KEY> address <REMOTE_PUBLIC_IP>

From the diagram:

R1 outside IP: 192.168.10.1/24

R2 outside IP: 192.168.20.2/24 remote peer for R1

In the current R1 configuration, the ISAKMP key is incorrectly bound to 192.168.10.2, which is a local next-hop/ISP address on R1's own subnet, not the R2 public IP. Because the pre-shared-key address does not match the source IP of R2's IKE packets, phase 1 negotiation fails and the tunnel never comes up.

The correct configuration on R1 must therefore be:

crypto isakmp key vpnuser address 192.168.20.2

Options A and C incorrectly change the default route (next hop must be the local ISP router, not R2's public IP or a LAN address). Option D uses an internal address (10.1.1.2), which is not the IP used for IKE on the Internet.