Guide-linked quiz · Medium Level
CUDA, Driver and Framework Version Compatibility Quiz
Separate host driver, toolkit and framework build versions, and choose a compatibility check that matches the deployment platform.
Question 1 of 8
Which component manages the physical GPU from the host operating system?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- Which component manages the physical GPU from the host operating system?
- The NVIDIA driver
- The framework wheel
- The model checkpoint
- The Python virtual environment
- What does a framework's CUDA build tag describe most directly?
- The exact host driver installed on every machine
- The CUDA support that framework package was built to use
- The version of the physical GPU firmware
- The model's training data format
- Why may nvcc --version differ from a driver utility's CUDA capability display?
- Both report the framework version
- One must be corrupted whenever values differ
- They report different layers: toolkit compiler versus driver-supported capability
- They both identify the GPU model only
- What does CUDA backward compatibility generally allow under documented conditions?
- An older driver can run applications built with a newer toolkit without a compatibility path
- Driver and toolkit versions must always have identical minor numbers
- A sufficiently new driver can run applications built with older CUDA toolkits
- Any toolkit build works with every older driver
- A framework imports, but a GPU operation fails. Which conclusion is warranted?
- The host driver must be correct
- Package import succeeded, but runtime compatibility still needs diagnosis
- The model checkpoint is incompatible by definition
- All CUDA libraries are initialized
- Where should an engineer verify a supported framework and CUDA combination?
- A container filename alone
- An arbitrary version string copied from another project
- The framework's official release installation guidance and NVIDIA compatibility documentation
- The newest toolkit regardless of framework build
- Why change one compatibility layer at a time during troubleshooting?
- It makes toolkit and driver versions identical
- It guarantees a newer driver works with every package
- It avoids recording versions
- It helps identify which change resolves or causes the failure
- What should a reproducible GPU bug report record?
- OS, GPU, host driver, image and framework build
- Only the framework's major version
- Only the displayed CUDA capability
- The user's password and model weights
Keep testing yourself
More quizzes picked for your level.