1Z0-1110-25 practice question 23 of 35

During a job run, you receive an error message that no space is left on your disk device. To solve the problem, you must increase the size of the job storage. What would be the most efficient way to do this with Data Science Jobs?

Full set: 307 questions

Answer options

A: Edit the job, change the size of the storage of your job, and start a new job run

B: On the job run, set the environment variable that helps increase the size of the storage

C: Create a new job with increased storage size and then run the job Correct answer

D: Your code using too much disk space. Refactor the code to identify the problem

Correct Answer:

C. Create a new job with increased storage size and then run the job

Explanation

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".

Keep practicing

Take the free 1Z0-1110-25 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test