mediumMultiple Choice
350-401 Practice Question: An engineer is managing a Cisco NFVIS host…
An engineer is managing a Cisco NFVIS host running multiple virtual network functions (VNFs). The engineer needs to upgrade the NFVIS software to a new version that includes critical security patches. The upgrade process must minimize downtime. Which upgrade method should the engineer use?
⚠ Common exam trap
Cisco often tests the misconception that NFVIS upgrades can be applied without a reboot, but the correct method always requires a single reboot to activate the new software version.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the 'software install add' command to stage the image, then 'activate' and 'commit' with a single reboot.
The 'software install add' command stages the new NFVIS image, followed by 'activate' and 'commit' with a single reboot, which minimizes downtime by performing the upgrade in a single reboot cycle. This method is the recommended approach for upgrading NFVIS while preserving existing VNF configurations and minimizing service disruption.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the 'patch install' command to apply the upgrade without rebooting.
Why it's wrong here
The 'patch install' command is not part of the NFVIS software lifecycle; NFVIS upgrades use the 'software install' command set, not a patch mechanism. Also, NFVIS does not support live patching — any software upgrade requires a reboot to load the new kernel and services. Therefore, attempting to apply an upgrade without rebooting is not a valid procedure.
- ✓
Use the 'software install add' command to stage the image, then 'activate' and 'commit' with a single reboot.
Why this is correct
This is the correct upgrade workflow: 'software install add' stages the image onto the device, 'activate' makes it the next boot image, and 'commit' finalizes the change. The entire process triggers a single reboot, which is the intended way to apply NFVIS upgrades while minimizing downtime. This is the only supported method for in-place NFVIS upgrades.
- ✗
Perform a clean installation of the new NFVIS version and redeploy all VNFs.
Why it's wrong here
A clean installation destroys the existing NFVIS configuration and VNFs, forcing you to redeploy everything from scratch. This approach is not recommended because it maximizes downtime and operational risk compared to an in-place upgrade. Moreover, it is not a software upgrade procedure—it is a disaster-recovery or new-deployment process, not a routine upgrade path.
- ✗
Migrate all VNFs to another NFVIS host, then upgrade the original host.
Why it's wrong here
Migrating all VNFs to another NFVIS host requires a separate, pre-configured host and is not a built-in upgrade command. This approach is a manual maintenance procedure that requires additional hardware and does not upgrade the NFVIS software itself; you still have to upgrade the original host afterward. Therefore, it is not the standard or recommended method for upgrading a single NFVIS node.
Go deeper
Related to this question
About these practice questions
This 350-401 question is part of Courseiva's 1,923-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 350-401 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-401 exam.