Detailed Answer in Step-by-Step Solution:
Objective: Efficiently increase storage for an OCI Job.
Understand Jobs: Storage (block volume) is set at job creation, not dynamically adjustable. Evaluate
Options:
A: False—Jobs can’t edit storage post-creation; it’s fixed. B: False—No environment variable adjusts
storage size.
C: True—Create a new job with larger storage (e.g., 200 GB) and run it. D: False—Refactoring code is
inefficient compared to increasing storage. Reasoning: C is the standard OCI process for adjusting
resources.
Conclusion: C is correct.
OCI documentation states: “Storage size for a Data Science Job is specified during job creation (e.g.,
block volume size). To increase it, create a new job with a larger storage configuration and initiate a new
run.” Editing (A) isn’t supported, variables (B) don’t apply, and refactoring (D) avoids the issue— only C
is efficient.
: Oracle Cloud Infrastructure Data Science Documentation, "Jobs - Storage Configuration".
