Question 10
During a security and capacity review at a financial analytics firm, engineers report the following issue: The team confuses the CUDA runtime with the Kubernetes control plane. The affected work supports risk scoring and historical-data models; traceable controls and predictable throughput are required. Choose TWO: one corrective approach and one result demonstrating it works. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Identify CUDA and a compatible driver and runtime as the GPU-compute programming stack, while keeping host orchestration distinct from parallel device kernels. This fits the specific reported issue: The team confuses the CUDA runtime with the Kubernetes control plane. The corresponding failure being reduced is: A GPU-equipped system will not accelerate unsupported code simply because a CUDA toolkit is installed; device execution and compatibility must be verified.
Correct independent evidence. A small parallel kernel runs on the GPU under a supported driver and the profiler distinguishes host control from device work. This verifies the corrective approach for the affected risk scoring and historical-data models instead of treating an architecture diagram alone as success.
Incorrect Answers
Not the most direct the action-and-evidence pair for these facts. A new input distribution is detected, attributed to a model version and evaluated through an approved retraining and rollback process. This choice concerns production mlops deployment and feedback loop and may be valid in another design. But this case reports 'The team confuses the CUDA runtime with the Kubernetes control plane', which calls for reasoning about cuda programming model for parallel applications. The targeted response is: Identify CUDA and a compatible driver and runtime as the GPU-compute programming stack, while keeping host orchestration distinct from parallel device kernels.
Not the most direct the action-and-evidence pair for these facts. Check NVIDIA driver, CUDA runtime, framework build and GPU support together before choosing a software combination for an accelerated workload. This choice concerns driver runtime and framework compatibility and may be valid in another design. But this case reports 'The team confuses the CUDA runtime with the Kubernetes control plane', which calls for reasoning about cuda programming model for parallel applications. The targeted response is: Identify CUDA and a compatible driver and runtime as the GPU-compute programming stack, while keeping host orchestration distinct from parallel device kernels.
Not the most direct the action-and-evidence pair for these facts. Evaluate request latency, concurrency, batching and model size together when selecting inference resources, with measurements under a representative service-level target. This choice concerns inference latency throughput and batching tradeoffs and may be valid in another design. But this case reports 'The team confuses the CUDA runtime with the Kubernetes control plane', which calls for reasoning about cuda programming model for parallel applications. The targeted response is: Identify CUDA and a compatible driver and runtime as the GPU-compute programming stack, while keeping host orchestration distinct from parallel device kernels.