Question 30
A job logs under an employee's identity on a local compute instance but fails on a managed cluster when reading storage. Which setting should be inspected?
Explanation
Correct Answer
Job identity can differ from interactive user identity; runtime access must be granted explicitly to the executing context.
Incorrect Answers
The alternative, Request the correct VM-family core quota or select another permitted SKU, belongs to a different technical condition: A newly created high-memory training cluster stays at zero capacity after all jobs enter the queue. The quota page reports zero remaining cores in that VM family. There the source-specific mechanism or proof is: Cluster scaling is bounded by regional and VM-family quota; queued work cannot create unavailable cores automatically. The condition asked about here is: A job logs under an employee's identity on a local compute instance but fails on a managed cluster when reading storage. A suitable correction is Assign and grant data access to the appropriate managed identity for the compute execution; the targeted justification or result is: Job identity can differ from interactive user identity; runtime access must be granted explicitly to the executing context.
Use an autoscaling compute cluster with minimum node count set to zero. That operation would be relevant if: A team submits many short training jobs and wants nodes to scale down to zero when no jobs remain. Its corresponding reason or verification is: Managed compute clusters can provision capacity for jobs and scale back when idle, reducing unnecessary compute charges. However the problem in this question is: A job logs under an employee's identity on a local compute instance but fails on a managed cluster when reading storage. The requirement instead calls for Assign and grant data access to the appropriate managed identity for the compute execution; the question-specific check is: Job identity can differ from interactive user identity; runtime access must be granted explicitly to the executing context.
Choose a supported GPU compute target with the necessary GPU quota and runtime. A separate source case supports that approach when: A deep-learning job cannot start on the selected CPU-only cluster because CUDA acceleration is required. The supporting rationale or observable result is: GPU training needs compatible hardware and drivers; changing the model display name cannot provide CUDA capacity. This question describes a different issue: A job logs under an employee's identity on a local compute instance but fails on a managed cluster when reading storage. Address it through Assign and grant data access to the appropriate managed identity for the compute execution, with the required justification or evidence: Job identity can differ from interactive user identity; runtime access must be granted explicitly to the executing context.