Detailed Answer in Step-by-Step Solution:

Objective: Identify a true statement about OCI Jobs logging.

Understand Logging: Jobs can log stdout/stderr to OCI Logging service.

Evaluate Options:

A: False—Each run has its own log, not a single job log.

B: False—Logging is optional, not mandatory.

C: True—When enabled, stdout/stderr are auto-captured.

D: False—Logs persist unless explicitly deleted.

Reasoning: C matches OCI’s automatic logging feature.

Conclusion: C is correct.

OCI documentation states: “When automatic log creation is enabled for Data Science Jobs, all stdout and stderr outputs are captured and stored in the OCI Logging service.” A is incorrect (per-run logs), B is optional, and D contradicts log retention—only C is accurate.

Oracle Cloud Infrastructure Data Science Documentation, "Jobs Logging".

Detailed Answer in Step-by-Step Solution:

Objective: Select an ADSTuner strategy to minimize cost and assess model quality.

Understand ADSTuner: Optimizes hyperparameters with configurable search spaces.

Evaluate Options:

A: Detailed—Exhaustive, high cost—incorrect.

B: No search space—False; tuning requires a space.

C: Perfunctory—Quick, low-cost assessment—correct.

D: Dictionary—Defines space but not a strategy.

Reasoning: Perfunctory balances cost and initial quality check.

Conclusion: C is correct.

OCI documentation states: “ADSTuner’s perfunctory strategy (C) performs a quick, low-cost search to assess model quality, ideal for initial tuning.” Detailed (A) is costly, B misstates requirements, and D is a method, not a strategy—only C fits the goal.

Oracle Cloud Infrastructure ADS SDK Documentation, "ADSTuner Search Strategies".

Detailed Answer in Step-by-Step Solution:

Objective: Efficiently manage varying hyperparameters in OCI Data Science Jobs.

Understand OCI Jobs: Jobs execute predefined tasks with configurable inputs (e.g., env vars, args).

Evaluate Options:

A: New job per run with env vars—Redundant job creation, inefficient.

B: New job per run with args—Similarly inefficient due to repeated setup.

C: Hardcode params, new job per change—Highly inefficient, requires code edits.

D: Single job, flexible params via env vars or args—Efficient, reusable—correct.

Reasoning: D minimizes job creation, allows runtime flexibility via configuration—best practice.

Conclusion: D is correct.

OCI documentation states: “For Jobs with varying hyperparameters, write code to accept environment variables or command-line arguments (D), then configure these per Job Run using the OCI Console or SDK—most efficient approach.” Options A, B, and C involve unnecessary job proliferation or code changes—only D aligns with OCI’s design for parameterized runs.

Oracle Cloud Infrastructure Data Science Documentation, "Configuring Job Runs with Parameters".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the OCI service for scalable Spark applications.

Evaluate Options:

A: Data Science—ML platform, not Spark-focused.

B: Anomaly Detection—Specific ML service, not general Spark.

C: Data Labeling—Annotation tool, not Spark-related.

D: Data Flow—Managed Spark service for big data.

Reasoning: Data Flow is OCI’s Spark execution engine.

Conclusion: D is correct.

OCI Data Flow “provides a fully managed environment to run Apache Spark applications at scale, ideal for data processing and ML tasks.” Data Science (A) supports Spark in notebooks, but Data Flow (D) is the dedicated, scalable solution—B and C are unrelated.

Oracle Cloud Infrastructure Data Flow Documentation, "Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Select an OCI AI service for text and table extraction from documents.

Evaluate Options:

A: Language—Text analysis, not extraction—incorrect.

B: Digital Assistant—Chatbots, not document tasks—incorrect.

C: Speech—Audio transcription, not documents—incorrect.

D: Vision—OCR for text/tables—correct.

Reasoning: Vision’s OCR extracts text and tables from document images.

Conclusion: D is correct.

OCI documentation states: “OCI Vision (D) uses OCR to extract text and tables from documents, supporting document analysis tasks.” A analyzes text post-extraction, B and C are unrelated—only D fits per OCI’s AI services.

Oracle Cloud Infrastructure Vision Documentation, "Document Analysis Features".

Detailed Answer in Step-by-Step Solution:

Understand OCI Data Labeling Capabilities: OCI Data Labeling is designed to annotate data for machine learning, supporting specific file types like images, text documents, and videos.

Evaluate Options:

A. Video footage: Supported for tasks like object detection or action recognition.

B. Images: Supported for image classification, object detection, etc.

C. Typewritten document: Supported as text data for tasks like entity extraction or classification.

D. Purchase orders: While potentially text-based, this is ambiguous without format clarification (e.g., PDF, image). OCI supports text annotation, but “purchase orders” isn’t a specific file type—it’s assumed as text here.

E. Audio recording: Not supported, as OCI Data Labeling focuses on visual and textual data, not audio.

Select Three: A (video), B (images), and C (text documents) are explicitly supported file types.

OCI Data Labeling supports annotating datasets of images, text, and videos, as per the official documentation. Video footage (A) can be annotated for tasks like object tracking, images (B) for classification or detection, and typewritten documents (C) for text-based annotations (e.g., named entity recognition). Audio files (E) are not supported, and while purchase orders (D) could be text, the question specifies “typewritten document” as a clearer match. (Reference: Oracle Cloud Infrastructure Data Labeling Service Documentation, "Supported Data Types").

Detailed Answer in Step-by-Step Solution:

Understand ORM Template: It automates OCI Data Science setup with predefined configurations.

Evaluate Components:

A: User groups are created for role-based access—automated.

B: Dynamic groups (e.g., for notebook sessions) are included—automated.

C: Individual users require manual creation via IAM—not automated.

D: Basic policies (e.g., access to Data Science resources) are included—automated.

Reasoning: ORM focuses on infrastructure and permissions, not user accounts.

Conclusion: C is the exception.

The OCI Resource Manager template for Data Science “automatically provisions user groups, dynamic groups, and policies for basic use cases,” but “individual users must be created separately in IAM and assigned to groups.” C is the only item not handled by the template, per the documentation.

Oracle Cloud Infrastructure Resource Manager Documentation, "Data Science Template".

Detailed Answer in Step-by-Step Solution:

Objective: Encode categorical features in a Data Science context (likely ADS SDK).

Understand Encoding: Converts categories (e.g., countries) to numerical forms.

Evaluate Options:

A: Not a standard ADS method—incorrect.

B: General transformation, not specific encoding—incorrect.

C: OneHotEncoder—Standard for categorical encoding—correct.

D: Visualization, not encoding—incorrect.

Reasoning: One-hot encoding creates binary columns—ideal for multiple categories.

Conclusion: C is correct.

OCI documentation states: “In ADS SDK, use OneHotEncoder (C) from sklearn (or similar) to encode categorical features like ‘countries’ into binary vectors for modeling.” A isn’t real, B is too broad, D is unrelated—only C fits OCI’s encoding practice.

Oracle Cloud Infrastructure Data Science Documentation, "Feature Encoding with ADS".

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

Detailed Answer in Step-by-Step Solution:

Understand OCI Anomaly Detection: This service trains models to detect anomalies in multivariate data (e.g., sensor readings), requiring data to be accessible within OCI’s ecosystem.

Assess Storage Requirements: The training data must be in a scalable, OCI-compatible location that the Anomaly Detection service can access programmatically.

Evaluate Options:

A. Your local machine: Data on a local machine isn’t directly accessible to OCI services without upload, making it impractical for cloud-based training.

B. MySQL database: While OCI supports MySQL, Anomaly Detection doesn’t natively integrate with it for training data; it prefers file-based input.

C. Autonomous Data Warehouse: This is a database for analytics, not the default storage for Anomaly Detection training data, which expects CSV/JSON files.

D. Object Storage Bucket: OCI Object Storage is a scalable, durable storage service that Anomaly Detection uses to ingest training data (e.g., CSV files).

Reasoning: Object Storage is the standard for large-scale data in OCI services, offering seamless integration with Anomaly Detection via APIs or SDKs.

Conclusion: D is the correct choice as it aligns with the service’s architecture.

The OCI Anomaly Detection service requires training data to be uploaded to an Object Storage Bucket in formats like CSV or JSON. This is explicitly outlined in the official documentation, which states that users must “upload the training dataset to an OCI Object Storage bucket” before creating a data asset for model training. Local storage (A) isn’t viable for cloud processing, and databases like MySQL (B) or Autonomous Data Warehouse (C) aren’t supported as primary inputs. Object Storage (D) provides the scalability and accessibility needed for multivariate anomaly detection workflows.

Oracle Cloud Infrastructure Anomaly Detection Documentation, "Preparing Training Data" section.