NCP-AIO Installation and Deployment Practice Question
A system administrator is installing the NVIDIA Container Toolkit on a standalone Ubuntu server to run GPU-accelerated containers. After installation, they want to verify that the toolkit is correctly configured. Which command should they run to test GPU access from a container?
⚠ Common exam trap
The trap here is assuming that running nvidia-smi on the host or checking the toolkit version is sufficient to verify container GPU access, when a container-based test is required.
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
✓
docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
To verify that the NVIDIA Container Toolkit is correctly configured, the administrator should run a container with GPU access and execute nvidia-smi inside it. The command docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi uses the --gpus all flag to expose all GPUs, and the nvidia-smi output confirms that the container can see and use the GPUs. This tests the entire stack from Docker to the toolkit. Other commands only check installation or host-level GPU status.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
Why this is correct
This command runs a CUDA container with all GPUs exposed and executes nvidia-smi inside the container. If the toolkit is configured correctly, the container will have access to the GPUs and nvidia-smi will display them. This directly tests the container runtime's ability to pass through GPU devices. It is the standard method to verify NVIDIA Container Toolkit functionality.
- ✗
nvidia-smi
Why it's wrong here
nvidia-smi is a host utility that displays GPU information, but it does not test container GPU access. It runs on the host and shows the driver status. While it is useful for verifying the driver, it does not confirm that the NVIDIA Container Toolkit is properly configured for containers. The administrator needs a container-based test to validate the toolkit.
- ✗
systemctl status nvidia-container-runtime
Why it's wrong here
systemctl status nvidia-container-runtime checks the status of the nvidia-container-runtime service, but this service is not typically run as a systemd service. The runtime is invoked by the container engine, not managed as a standalone service. This command would likely return no such service, and even if it existed, it would not test actual GPU access from a container.
- ✗
nvidia-container-cli --version
Why it's wrong here
nvidia-container-cli --version displays the version of the NVIDIA Container Toolkit's CLI tool, but it does not test GPU access from a container. It only confirms that the toolkit is installed. It does not verify that the runtime is correctly configured to expose GPUs to containers. Therefore, it is insufficient for the verification task.
About these practice questions
One of 309 original NCP-AIO practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official NVIDIA exam blueprint
This NCP-AIO practice question is part of Courseiva's free NVIDIA 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 NCP-AIO exam.