Oracle 1z0-1110-25 Oracle Cloud Infrastructure 2025 Data Science Professional Exam Practice Test

Detailed Answer in Step-by-Step Solution:

Objective: Identify two methods to enhance Object Storage durability.

Understand Durability: Ensures data isn’t lost—focus on redundancy and protection.

Evaluate Options:

A: RAID1—Block volume feature, not Object Storage.

B: Encryption—Secures data, not durability.

C: Versioning—Retains old versions, prevents loss—correct.

D: Limit delete—Prevents accidental deletion—correct.

E: Client encryption—Secures, not durability-focused.

Reasoning: C and D directly protect against data loss—durability-focused.

Conclusion: C and D are correct.

OCI documentation states: “Improve Object Storage durability with Versioning (C) to retain previous object versions and by limiting delete permissions (D) to prevent accidental loss.” A isn’t applicable, B and E focus on security—only C and D enhance durability per OCI’s storage features.

Oracle Cloud Infrastructure Object Storage Documentation, "Data Durability Options".

Detailed Answer in Step-by-Step Solution:

Objective: Identify custom model types for OCI Language.

Understand OCI Language: Focuses on text analysis.

Evaluate Options:

A: Image classification—Not text-based, incorrect.

B: Text classification, NER—Both text tasks—correct.

C: Sentiment, NER—Sentiment is pretrained, not custom.

D: Object detection—Image-based, incorrect.

Reasoning: B aligns with OCI Language’s text custom models.

Conclusion: B is correct.

OCI Language documentation states: “Custom models can be trained for text classification and Named Entity Recognition (NER) using your data.” Image tasks (A, D) are for Vision, and sentiment (C) is pretrained—only B fits OCI Language’s scope.

Oracle Cloud Infrastructure Language Documentation, "Custom Model Training".

Detailed Answer in Step-by-Step Solution:

Objective: Identify an invalid notebook session practice.

Evaluate Options:

A: Valid—Long runs should use Jobs, not notebooks.

B: Valid—Terminal runs with logging are supported.

C: Valid—Multi-user conflicts are a concern.

D: Invalid—Copying from Object Storage to block volume is unnecessary; direct access is best.

E: Valid—Resource principals are secure and recommended.

Reasoning: D contradicts OCI’s direct-access efficiency.

Conclusion: D is incorrect.

OCI documentation advises: “Access data in Object Storage directly from notebook sessions using SDKs or resource principals—avoid local copies (D) unless necessary.” A, B, C, and E are best practices—D is inefficient and not standard.

Oracle Cloud Infrastructure Data Science Documentation, "Notebook Session Best Practices".

Detailed Answer in Step-by-Step Solution:

Objective: Optimize an embarrassingly parallel job in OCI Data Science Jobs.

Define Embarrassingly Parallel: Tasks are independent, ideal for simultaneous runs.

Evaluate Options:

A: Multiple simultaneous runs—Leverages parallelism—correct.

B: One job per run—Misstates capability; unnecessary complexity.

C: Sequential runs—Inefficient, ignores parallelism.

D: False—Jobs support parallelism.

Reasoning: A maximizes efficiency for parallel tasks.

Conclusion: A is correct.

OCI documentation states: “For embarrassingly parallel workloads, create a single Job and launch multiple simultaneous Job Runs to process data in parallel.” B misinterprets limits, C wastes time, and D denies capability—only A fits OCI’s design.

Oracle Cloud Infrastructure Data Science Documentation, "Parallel Job Runs".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the architecture with “never trust, always verify.”

Evaluate Options:

A: Federated identity—Shares auth, not verification-focused.

B: Zero trust—Explicitly “never trust, always verify”—correct.

C: Fluid perimeter—Adaptive, not the core principle.

D: Defense in depth—Layered, not verification-centric.

Reasoning: Zero trust matches the stated principle exactly.

Conclusion: B is correct.

OCI documentation states: “Zero trust (B) architecture operates on ‘never trust, always verify,’ requiring continuous authentication and authorization.” A, C, and D have different focuses—only B aligns with OCI’s security philosophy.

Oracle Cloud Infrastructure Security Documentation, "Zero Trust Architecture".

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:

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 a true statement about OCI Data Science Jobs.

Understand OCI Jobs: Jobs automate ML tasks (e.g., training) on managed infrastructure.

Evaluate Options:

A: True—Jobs provision OCI compute resources on-demand for task execution.

B: False—Users define custom tasks (e.g., Python scripts), not limited to standard ones.

C: False—Infrastructure is fully managed by OCI, not user-managed.

D: False—Multiple artifacts (e.g., ZIP with dependencies) can be used, not just one file.

Reasoning: A reflects OCI’s managed, on-demand provisioning model for Jobs.

Conclusion: A is correct.

The OCI Data Science documentation states: “Jobs provision compute infrastructure on-demand to execute user-defined tasks, such as model training or data processing, on fully managed OCI resources.” B is incorrect (customization is allowed), C contradicts the managed nature, and D misstates artifact flexibility—only A accurately describes Jobs.

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

Detailed Answer in Step-by-Step Solution:

Objective: Efficiently vary hyperparameters in OCI Jobs.

Evaluate Options:

A: New job per run—Wastes setup time.

B: Code changes per job—Inefficient, error-prone.

C: Flexible params per run—Efficient, reusable—correct.

D: New job per run—Redundant effort.

Reasoning: C minimizes job creation, maximizes flexibility.

Conclusion: C is correct.

OCI documentation states: “For varying hyperparameters, configure a single Job with code accepting environment variables or command-line arguments (C), set per run—most efficient.” A and D over-create jobs, B ties params to code—only C optimizes.

Oracle Cloud Infrastructure Data Science Documentation, "Job Parameterization".

Detailed Answer in Step-by-Step Solution:

Objective: Identify OCI’s managed Kubernetes service.

Evaluate Options:

A: Container Registry—Stores images, not Kubernetes.

B: Load Balancing—Network service, not Kubernetes.

C: Container Engine (OKE)—Managed Kubernetes—correct.

D: Streaming—Data streaming, not containers.

Reasoning: C is OCI’s Kubernetes offering—OKE.

Conclusion: C is correct.

OCI documentation states: “OCI Container Engine for Kubernetes (OKE) (C) provides a managed service to deploy, scale, and manage containerized applications using Kubernetes.” A, B, and D serve other purposes—only C matches per OCI’s container services.

Oracle Cloud Infrastructure OKE Documentation, "Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the interactive coding environment in OCI Data Science.

Evaluate Options:

A: Model Catalog stores models—not for coding.

B: Jobs run predefined tasks—not interactive.

C: Notebook Sessions provide JupyterLab for coding and training—interactive.

D: Projects organize work—not a coding environment.

Reasoning: Notebook Sessions are OCI’s Jupyter-based tool for interactive ML development.

Conclusion: C is correct.

OCI Data Science Notebook Sessions “provide an interactive JupyterLab environment where data scientists can write code, explore data, and train machine learning models.” Model Catalog (A) is for storage, Jobs (B) for automation, and Projects (D) for organization—only C offers interactivity.

Oracle Cloud Infrastructure Data Science Documentation, "Notebook Sessions Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Share a custom conda environment in OCI Data Science.

Understand Commands: OCI provides odsc CLI for environment management.

Evaluate Options:

A: clone duplicates an environment locally—not for sharing.

B: publish uploads the environment to Object Storage for team access—correct.

C: modify doesn’t exist as a standard command.

D: install sets up an environment locally—not for sharing.

Reasoning: Sharing requires publishing to a shared location (Object Storage), which publish achieves.

Conclusion: B is the correct command.

The OCI Data Science CLI documentation states: “Use odsc conda publish to package and upload a custom conda environment to an Object Storage Bucket, making it accessible to other users.” clone (A) is for local duplication, modify (C) isn’t valid, and install (D) is for local setup—not sharing. B is the designated sharing mechanism.

Oracle Cloud Infrastructure Data Science CLI Reference, "odsc conda publish".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the OCI service for ML model lifecycle.

Evaluate Options:

A: Data Catalog—Metadata management, not ML.

B: Data Integration—ETL, not ML.

C: Data Science—Full ML lifecycle—correct.

D: Data Flow—Spark processing, not full ML.

Reasoning: C supports building, training, deploying models.

Conclusion: C is correct.

OCI documentation states: “OCI Data Science (C) provides tools to build, train, and deploy machine learning models in the cloud, including notebooks and model catalog.” A, B, and D serve other purposes—only C fits the ML lifecycle per OCI’s offerings.

Oracle Cloud Infrastructure Data Science Documentation, "Service Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Choose an interface for a Python script to manage projects.

Evaluate Options:

A: OCI SDK—Python-based, scriptable—correct.

B: Console—GUI, not scriptable.

C: CLI—Command-based, not Python-native.

D: Mobile App—Not for scripting.

Reasoning: A enables programmatic project creation.

Conclusion: A is correct.

OCI documentation states: “Use the OCI Python SDK (A) to programmatically manage Data Science resources, like creating projects, via Python scripts.” B, C, and D don’t support Python scripting—only A fits.

Oracle Cloud Infrastructure SDK Documentation, "Data Science API".

Detailed Answer in Step-by-Step Solution:

Objective: Optimize compute shape for cost and time.

Evaluate Options:

A: Tuning params—Focuses on model, not shape.

B: Strongest shape—Costly, unbalanced.

C: Scale up when utilized—Balances cost/time—correct.

D: Random start—Unsystematic.

Reasoning: C iteratively optimizes based on utilization.

Conclusion: C is correct.

OCI documentation advises: “Start with a small shape, monitor utilization and time (C); scale up if fully utilized until performance stabilizes—optimizes cost and speed.” A misfocuses, B overspends, D lacks method—only C aligns.

Oracle Cloud Infrastructure Data Science Documentation, "Compute Shape Optimization".

Detailed Answer in Step-by-Step Solution:

Objective: Assess if bias is a common issue in data science.

Define Bias: Systematic errors in data/models (e.g., skewed training data).

Evaluate Statement:

Bias arises from unrepresentative data, poor feature selection, or algorithmic flaws—widely recognized in ML.

Examples: Gender bias in hiring models, racial bias in facial recognition.

Reasoning: Literature and practice (e.g., fairness in AI) confirm bias as prevalent.

Conclusion: A (True) is correct.

OCI documentation notes: “Bias is a common challenge in data science, stemming from imbalanced datasets or flawed assumptions, requiring techniques like re-weighting or fairness checks.” This aligns with industry standards—bias is a well-documented issue, making A true.

Oracle Cloud Infrastructure Data Science Documentation, "Addressing Bias in Models".

Detailed Answer in Step-by-Step Solution:

Objective: Find optimal compute shape balancing cost and time.

Approach: Iterative testing with metrics (e.g., CPU/memory usage, runtime).

Evaluate Options:

A: Tuning parameters when underutilized—focuses on model, not shape optimization.

B: Strongest shape—Costly, ignores balance; overkill likely.

C: Scale up from small shape when fully utilized—Balances cost/time effectively.

D: Random start with pre-tests—Unsystematic and inefficient.

Reasoning: C incrementally increases resources based on utilization, optimizing both factors.

Conclusion: C is correct.

OCI documentation advises: “To optimize compute shape for Jobs, start with a small shape, monitor utilization (e.g., CPU, memory) and runtime via OCI Monitoring. If fully utilized, scale up until performance plateaus—balancing cost and speed.” A misfocuses on model tuning, B wastes cost, and D lacks structure—only C aligns with this method.

Oracle Cloud Infrastructure Data Science Documentation, "Optimizing ComputeShapes for Jobs".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the function that measures the difference between predicted and actual values in machine learning.

Understand ML Functions:

Optimizer function: Adjusts model parameters to minimize error (e.g., gradient descent)—it uses the cost, not defines it.

Fit function: Trains the model by fitting it to data—process-oriented, not a measure.

Update function: Typically updates weights during training—not a standard term for error measurement.

Cost function: Quantifies prediction error (e.g., MSE, cross-entropy)—directly represents the difference.

Evaluate Options:

A: Optimizer minimizes the cost, not the cost itself—incorrect.

B: Fit executes training, not error definition—incorrect.

C: Update is vague and not a standard ML term for this—incorrect.

D: Cost function (e.g., loss) measures prediction vs. target—correct.

Reasoning: The cost function (or loss function) is the mathematical representation of error, guiding optimization.

Conclusion: D is the correct answer.

In OCI Data Science, the documentation explains: “The cost function (or loss function) measures the difference between the model’s predicted values and the actual target values, such as mean squared error for regression or cross-entropy for classification.” Optimizers (A) use this to adjust weights, fit (B) is a training step, and update (C) isn’t a defined function here—only the cost function (D) fits the description. This aligns with standard ML terminology and OCI’s AutoML processes.

Oracle Cloud Infrastructure Data Science Documentation, "Machine Learning Concepts - Cost Functions".

Detailed Answer in Step-by-Step Solution:

Objective: Identify two reasons for key rotation in OCI Vault.

Understand Key Rotation: Enhances security by updating keys.

Evaluate Options:

A: Five-key limit—False, no such restriction.

B: Efficiency—False, not the purpose.

C: Reuse—False, rotation prevents reuse.

D: Reduces risk—True, limits exposure—correct.

E: Limits data—True, reduces breach scope—correct.

Reasoning: D and E are security-focused—key Vault benefits.

Conclusion: D and E are correct.

OCI documentation states: “Key rotation in Vault (D) reduces risk if a key is compromised and (E) limits the data encrypted by a single key version, enhancing security.” A, B, and C misrepresent rotation’s purpose—only D and E align with OCI’s Vault best practices.

Oracle Cloud Infrastructure Vault Documentation, "Key Rotation Benefits".

Detailed Answer in Step-by-Step Solution:

Objective: Identify Apache Spark’s ML library.

Understand Spark: A big data framework with specialized libraries.

Evaluate Options:

A: MLib (correctly MLlib)—Spark’s machine learning library.

B: GraphX—Graph processing, not ML.

C: Structured Streaming—Streaming data, not ML.

D: HadoopML—Not a Spark library (Hadoop-related).

Reasoning: MLlib is Spark’s official ML toolkit (e.g., regression, clustering).

Conclusion: A is correct (noting “MLib” should be “MLlib”).

OCI Data Science supports Spark via Data Flow, where “MLlib (Machine Learning library) provides scalable ML algorithms.” GraphX (B) and Structured Streaming (C) serve other purposes, and HadoopML (D) isn’t real—MLlib (A) is the standard, despite the typo.

Oracle Cloud Infrastructure Data Flow Documentation, "Apache Spark MLlib".

Detailed Answer in Step-by-Step Solution:

Objective: Identify a widely accepted maxim about data scientists’ time allocation.

Understand Data Science Workflow: Involves data collection, preparation, and analysis—time distribution is key.

Evaluate Options:

A: 80% on finding/preparing, 20% analyzing—Reflects the data wrangling challenge.

B: 80% analyzing, 20% finding/preparing—Inverts the common perception.

C: 80% on failed projects, 20% useful—Pessimistic, not a standard maxim.

Reasoning: Industry consensus (e.g., “80/20 rule”) emphasizes data prep as the bulk of effort due to messy real-world data.

Conclusion: A is correct.

OCI Data Science documentation aligns with industry norms: “Data scientists typically spend 80% of their time finding, cleaning, and preparing data, and 20% on analysis and modeling, due to the complexity of raw data.” B reverses this, and C isn’t supported—only A reflects this widely cited maxim from sources like Forbes and OCI’s practical guidance.

Oracle Cloud Infrastructure Data Science Documentation, "Data Science WorkflowOverview".

Detailed Answer in Step-by-Step Solution:

Objective: Identify three data formats supported by ADS SDK for loading data.

Understand ADS SDK: Facilitates data loading into notebook sessions via DatasetFactory.

Evaluate Options:

A. DOCX: Not natively supported—requires conversion (e.g., to text).

B. Pandas DataFrame: Supported—core format for data manipulation in ADS.

C. JSON: Supported—common structured data format.

D. Raw Images: Not directly supported—image data needs preprocessing (e.g., via Vision).

E. XML: Supported—parseable structured format.

Reasoning: ADS focuses on tabular/structured data—B, C, E align; A and D require external handling.

Conclusion: B, C, E are correct.

OCI documentation states: “ADS SDK’s DatasetFactory supports loading data from formats like Pandas DataFrames (B), JSON (C), and XML (E), enabling easy integration into notebook sessions.” DOCX (A) isn’t natively handled, and raw images (D) require preprocessing outside ADS—B, C, E match the supported list.

Oracle Cloud Infrastructure ADS SDK Documentation, "Supported Data Formats".

Detailed Answer in Step-by-Step Solution:

Define Feature Engineering: It’s the process of creating or modifying features to improve model performance.

Evaluate Options:

A: Parameter tuning adjusts model hyperparameters (e.g., learning rate), not features.

B: Model interpretation (e.g., SHAP values) explains predictions, not feature creation.

C: Transforming features (e.g., normalizing, encoding) is the core of feature engineering—correct.

D: Understanding features occurs during exploration, not engineering.

Reasoning: Feature engineering directly manipulates data inputs (e.g., converting timestamps to day-of-week), distinct from tuning or interpretation.

Conclusion: C is the precise definition.

OCI Data Science documentation defines feature engineering as “the process of transforming raw data into features that better represent the underlying problem to the predictive models, resulting in improved model accuracy.” Examples include scaling or creating interaction terms, aligning with C. Other options (A, B, D) relate to different ML stages.

Oracle Cloud Infrastructure Data Science Documentation, "Feature Engineering Overview".

Detailed Answer in Step-by-Step Solution:

Step 1: Install, configure, and authenticate Git: Git must be installed and configured (e.g., git config --global user.name) before any repository actions.

Step 2: Configure SSH keys: SSH keys are set up (e.g., ssh-keygen) and added to the remote service (e.g., GitHub, OCI Code Repository) for secure access.

Step 3: Create local and remote Git repository: Initialize a local repo (git init) and create/link a remote repo (e.g., git remote add origin).

Step 4: Commit files: Add files (git add .) and commit them locally (git commit -m "message").

Step 5: Push to remote: Push local commits to the remote repo (git push origin main).

Evaluate Options: Only D (1, 2, 3, 4, 5) follows this logical sequence; others (e.g., A starts with SSH before Git installation) are illogical.

The standard Git workflow in OCI Data Science or general practice begins with installing Git (1), configuring SSH for secure access (2), creating repositories (3), committing locally (4), and pushing remotely (5). The OCI Code Repository documentation aligns with this: “First, install Git and configure authentication (e.g., SSH), then set up repositories and manage code.” D is the only option reflecting this industry-standard process.

Oracle Cloud Infrastructure Code Repository Documentation, "Git Workflow Basics".

Detailed Answer in Step-by-Step Solution:

Define Conda: Conda is a widely used tool for managing packages and environments in data science.

Evaluate Options:

A: Partially true—Conda manages dependencies, but it’s broader (an environment system).

B: Incorrect—Kernels (e.g., Jupyter) are separate; Conda manages environments.

C: Correct—Conda is an open-source tool for creating isolated environments with specific packages.

D: Incorrect—Not specific to Oracle AI; it’s a general tool.

Reasoning: C captures Conda’s full scope as an open-source system, beyond just dependency management (A).

Conclusion: C is the most accurate.

OCI documentation describes Conda as “an open-source package and environment management system that allows data scientists to create isolated environments with specific versions of Python and libraries.” A is too narrow, B misaligns with kernel concepts, and D ties it incorrectly to Oracle AI. C aligns with Conda’s official definition and OCI’s usage.

Oracle Cloud Infrastructure Data Science Documentation, "Conda Environments Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Select an explanation technique for feature-target relationships with correlated features.

Evaluate Options:

A: Permutation—Breaks with high correlation.

B: LIME—Local, not global relationships.

C: Dependence—Not a standard term; vague.

D: ALE—Handles correlation, shows feature effects—correct.

Reasoning: ALE is robust to correlated features, ideal here.

Conclusion: D is correct.

OCI documentation states: “Accumulated Local Effects (ALE) (D) evaluates feature-target relationships, accounting for correlations, unlike permutation importance (A) which falters with high correlation.” B is local, C isn’t defined—only D fits per OCI’s explanation tools.

Oracle Cloud Infrastructure Data Science Documentation, "Model Explanation Techniques".

Detailed Answer in Step-by-Step Solution:

Objective: Identify encryption standard for OCI Data Science.

Understand OCI Encryption: Applies to data at rest and in transit.

Evaluate Options:

A: AES-256—Industry-standard, OCI default—correct.

B: DES—Outdated, weak—incorrect.

C: TDES—Older, less secure—incorrect.

D: Twofish—Not OCI standard—incorrect.

E: RSA—Asymmetric, not primary for data at rest—incorrect.

Reasoning: AES-256 is OCI’s go-to for Data Science resources.

Conclusion: A is correct.

OCI documentation states: “Data Science services encrypt data at rest using AES-256 (A), ensuring high security for notebooks, jobs, and models.” B, C, D, and E are either outdated or not used—only A matches OCI’s encryption policy.

Oracle Cloud Infrastructure Data Science Documentation, "Data Encryption".

Detailed Answer in Step-by-Step Solution:

Objective: Spot the invalid Security Zone policy.

Understand Security Zones: Enforce strict security—resources can’t leave easily.

Evaluate Options:

A: Boot volume move—Not allowed; violates zone rules—invalid.

B: Compute no-move—True, enforces security.

C: No public access—True, standard policy.

D: Auto-backup—True, required for compliance.

Reasoning: A contradicts Security Zone immutability.

Conclusion: A is incorrect.

OCI documentation states: “Resources like boot volumes (A) cannot be moved from a Security Zone to a standard compartment—B, C, and D are enforced policies.” A violates OCI’s Security Zone restrictions—only A is not valid.

Oracle Cloud Infrastructure Security Zones Documentation, "Policy Restrictions".

Detailed Answer in Step-by-Step Solution:

Objective: Identify common data science techniques.

Define Techniques:

Classification: Predicts categories (e.g., spam vs. not).

Regression: Predicts continuous values (e.g., sales).

Clustering: Groups data (e.g., customer segments).

Evaluate Options:

A, B, C: All are standard ML/statistical methods.

D: Encompasses all—correct as they’re widely used.

Reasoning: These are foundational in data science workflows.

Conclusion: D is correct.

OCI documentation lists “classification, regression, and clustering as core techniques in data science, supported by tools like ADS SDK and AutoML.” All (D) are common per OCI’s ML framework, not just subsets (A, B, C).

Oracle Cloud Infrastructure Data Science Documentation, "Analytical Techniques".

Detailed Answer in Step-by-Step Solution:

Objective: Determine truth about WAF origin management.

Understand WAF: Protects apps by routing traffic via origins.

Evaluate Statements:

A: Multiple origins—True; WAF supports this.

B: Single active origin—True; only one is active per policy.

Evaluate Options:

C: B only—False; A is true.

D: Both false—Incorrect.

E: Both true—Correct per OCI WAF.

F: A only—False; B is true.

Conclusion: E is correct.

OCI documentation states: “WAF allows defining multiple origins (A), but only one origin is active per WAF policy at a time (B)—both are true (E).” C, D, and F misalign—E matches OCI’s WAF origin management.

Oracle Cloud Infrastructure WAF Documentation, "Origin Management".

Detailed Answer in Step-by-Step Solution:

Objective: Identify three data types for OCI Data Labeling (question likely incomplete—assuming B, C, D, E options).

Understand Data Labeling: Annotates data for ML—focuses on specific types.

Evaluate Options (Assuming Typical Set):

A: Audio—Not supported—incorrect.

B: Text Document—Supported (e.g., NER)—correct.

C: Images—Supported (e.g., object detection)—correct.

D: Graphs—Not a standard type—incorrect.

Assumed E: Videos—Supported but missing—adjust to fit.

Reasoning: OCI supports text, images, and videos—question lists only four, so B and C are definite.

Conclusion: B, C (third likely video, missing).

OCI documentation states: “Data Labeling supports text documents (B), images (C), and videos for annotation—audio (A) and graphs (D) are not included.” Question likely meant three from a larger set; B and C are confirmed per OCI’s Data Labeling capabilities.

Oracle Cloud Infrastructure Data Labeling Documentation, "Supported Data Types".

Detailed Answer in Step-by-Step Solution:

Objective: Identify an open model format for cross-platform ML model execution.

Evaluate Options:

A. PySpark: A big data framework, not a model format.

B. PyTorch: An ML framework with its own format, not inherently cross-platform without conversion.

C. TensorFlow: An ML framework with its SavedModel format, not universally open across platforms.

D. ONNX: Open Neural Network Exchange, an open-source format for model interoperability across frameworks.

Reasoning: ONNX is designed for portability (e.g., convert PyTorch to ONNX, run in TensorFlow), unlike framework-specific options.

Conclusion: D is the correct choice.

ONNX (D) is “an open-source model format that enables interoperability between ML frameworks like PyTorch and TensorFlow,” per OCI documentation. PySpark (A) is a processing tool, while PyTorch (B) and TensorFlow (C) are frameworks with native formats—only ONNX ensures cross-platform compatibility.

Oracle Cloud Infrastructure Data Science Documentation, "Supported Model Formats".

Detailed Answer in Step-by-Step Solution:

Objective: Find a true statement about OCI Anomaly Detection.

Understand Service: Detects anomalies in multivariate data (e.g., time series).

Evaluate Options:

A: False—Accepted types are CSV/JSON, not SQL/Python.

B: Partially true—Focuses on numerical data (e.g., sensors), not text broadly.

C: True—Used for fraud, intrusions, and sensor anomalies (key use cases).

D: False—Trained on customer data only, not general datasets.

Reasoning: C aligns with documented applications; others misalign.

Conclusion: C is correct.

OCI Anomaly Detection documentation states: “The service is designed to detect anomalies in time series data, making it valuable for fraud detection, network intrusion analysis, and sensor discrepancies.” A is incorrect (file formats), B overgeneralizes (numerical focus), and D misstates training data—only C matches the service’s purpose.

Oracle Cloud Infrastructure Anomaly Detection Documentation, "Use Cases".

Detailed Answer in Step-by-Step Solution:

Objective: Find the OCI service for free geospatial images.

Evaluate Options:

A: Big Data Service—Spark processing, not datasets.

B: Analytics Cloud—Visualization, not data source.

C: Data Science—ML platform, not dataset provider.

D: Open Data—Free public datasets, including geospatial—correct.

Reasoning: Open Data is OCI’s public dataset hub.

Conclusion: D is correct.

OCI documentation states: “Oracle Open Data provides free access to curated datasets, including geospatial images, for public use.” A, B, and C serve other purposes—only D delivers free geospatial data.

Oracle Cloud Infrastructure Open Data Documentation, "Dataset Offerings".

Detailed Answer in Step-by-Step Solution:

Objective: Determine when an OCI Data Science pipeline can start.

Understand Pipelines: They’re workflows with defined steps, executed on demand or scheduled.

Evaluate Options:

A: Once created, a pipeline can be run immediately—correct.

B: “During run state” implies it’s already running—illogical.

C: “After active state” is unclear; pipelines run when triggered, not post-state.

D: “Before active state” is vague—creation precedes running.

Reasoning: Pipelines are executable post-creation via UI/CLI—simplest interpretation is A.

Conclusion: A is correct.

OCI Data Science documentation states: “After a pipeline is created, you can initiate a pipeline run immediately or schedule it using the OCI Console, CLI, or SDK.” B, C, and D misalign with this—running starts post-creation (A), not during/after ambiguous states.

Oracle Cloud Infrastructure Data Science Documentation, "Pipelines - Running a Pipeline".

Detailed Answer in Step-by-Step Solution:

Objective: Spot the invalid OCI IAM policy.

Understand Policies: Use verbs (e.g., use, manage) and resource types.

Evaluate Options:

A: Valid—virtual-network-family is a resource type.

B: Invalid—No data-science-model-sessions resource type; likely meant data-science-models.

C: Valid—data-science-projects is correct.

D: Valid—data-science-family aggregates Data Science resources.

Reasoning: B uses a nonexistent resource type—error in syntax.

Conclusion: B is incorrect.

OCI IAM documentation lists valid resource types: “data-science-models, data-science-projects, data-science-family—but not data-science-model-sessions (B).” A, C, D are correct—B is invalid due to this typo/misunderstanding.

Oracle Cloud Infrastructure IAM Documentation, "Data Science Resource Types".

Detailed Answer in Step-by-Step Solution:

Understand OCI Data Labeling Export: After annotation, datasets are exported for ML use.

Check Supported Formats: OCI Data Labeling exports annotations in a structured, machine-readable format.

Evaluate Options:

A: Binary isn’t a standard export format for annotations.

B: XML isn’t used; JSON is preferred for flexibility.

C: Line-delimited JSON is the correct format, aligning with ML workflows.

D: CSV is common but not the default for OCI Data Labeling.

Conclusion: C matches the official export format.

OCI Data Labeling exports annotated datasets as line-delimited JSON files, which store each annotation as a separate JSON object per line, suitable for ML pipelines. This is explicitly stated in the documentation. (Reference: Oracle Cloud Infrastructure Data Labeling Service Documentation, "Exporting Datasets").

Detailed Answer in Step-by-Step Solution:

Objective: Define data science’s main goal.

Evaluate Options:

A: Archiving—Not the focus; too narrow.

B: Analyze for insights/business value—Core purpose—correct.

C: Prep for analytics—Means, not the end goal.

D: Output-focused—Vague, incomplete.

Reasoning: B captures the actionable insight generation central to data science.

Conclusion: B is correct.

OCI documentation defines data science as “mining and analyzing large datasets to uncoveractionable insights for operational improvements and business value.” A is storage-focused, C is preparatory, and D is unclear—only B reflects the principal goal per OCI’s mission.

Oracle Cloud Infrastructure Data Science Documentation, "What is Data Science?".

Detailed Answer in Step-by-Step Solution:

Objective: Locate the lifecycle stage for transforming timestamps into categories.

Understand Lifecycle:

Model Type Selection: Choosing algorithms—post-data prep.

Model Validation: Evaluating performance—post-training.

Data Access: Retrieving raw data—pre-transformation.

Feature Engineering: Creating new features—correct.

Evaluate Options:

A: Too late—incorrect.

B: Post-model—incorrect.

C: Pre-transformation—incorrect.

D: Feature creation—correct.

Reasoning: Converting timestamps to time periods is feature engineering.

Conclusion: D is correct.

OCI documentation states: “Feature engineering (D) transforms raw data, such as timestamps into categorical variables (e.g., morning/afternoon), to enhance model inputs.” A, B, and C occur at different stages—only D fits OCI’s lifecycle for this task.

Oracle Cloud Infrastructure Data Science Documentation, "Feature Engineering Stage".

Detailed Answer in Step-by-Step Solution:

Objective: Identify two OCI-developed, non-open-source JupyterLab extensions.

Understand Extensions: OCI enhances JupyterLab with proprietary tools.

Evaluate Options:

A: Environment Explorer—OCI-specific, non-open—correct.

B: Table of Contents—Open-source Jupyter—incorrect.

C: Command Palette—Open-source Jupyter—incorrect.

D: Notebook Examples—OCI-specific, non-open—correct.

E: Terminal—Open-source Jupyter—incorrect.

Reasoning: A and D are OCI proprietary; others are standard JupyterLab.

Conclusion: A and D are correct.

OCI documentation states: “OCI Data Science adds non-open-source extensions like Environment Explorer (A) for conda management and Notebook Examples (D) for sample code—both proprietary enhancements.” B, C, and E are open-source JupyterLab defaults—only A and D are OCI-specific per the notebook session design.

Oracle Cloud Infrastructure Data Science Documentation, "JupyterLab Extensions".

Detailed Answer in Step-by-Step Solution:

Objective: Predict AutoML’s output when time runs out during tuning.

Understand AutoML Tuning: Iteratively tests hyperparameters, tracks best results.

Evaluate Options:

A: Best-known config—Logical, reflects optimization goal—correct.

B: Last config—Ignores prior better results—incorrect.

C: Minimum learning rate—Arbitrary, not performance-based.

D: Random—Defeats tuning purpose.

Reasoning: AutoML prioritizes the best config found within the budget.

Conclusion: A is correct.

OCI AutoML documentation states: “If the time budget expires, AutoML returns the best hyperparameter configuration (A) identified during tuning based on performance metrics.” Last (B), minimum (C), or random (D) configs aren’t selected—only A aligns with OCI’s optimization strategy.

Oracle Cloud Infrastructure AutoML Documentation, "Hyperparameter Tuning - Time Budget".

Detailed Answer in Step-by-Step Solution:

Objective: Identify custom model types for OCI Language service.

Understand OCI Language: Focuses on text analysis, not images.

Evaluate Options:

A: Image classification—Incorrect; Language is text-based.

B: Text classification, NER—Both text tasks—correct.

C: Sentiment—Pretrained, not custom; NER ok—incorrect.

D: Object detection—Image-based, incorrect.

Reasoning: B aligns with OCI Language’s custom text capabilities.

Conclusion: B is correct.

OCI documentation states: “OCI Language supports training custom models for text classification and Named Entity Recognition (NER) (B) using user data.” A and D involve images, C includes pretrained sentiment—only B matches OCI Language’s custom model scope.

Oracle Cloud Infrastructure Language Documentation, "Custom Model Types".

Detailed Answer in Step-by-Step Solution:

Objective: Find the OCI service for accessing large public datasets.

Evaluate Options:

A: Oracle Databases—General-purpose, not dataset-focused.

B: ADW—Analytics warehouse, not a dataset repository.

C: OCI Data Science—ML platform, not a dataset provider.

D: Oracle Open Data—Free, public datasets (e.g., geospatial).

Reasoning: Open Data provides pre-existing large datasets for research.

Conclusion: D is correct.

OCI documentation states: “Oracle Open Data provides free access to large, curated datasets, such as geospatial data, ideal for researchers.” Databases (A) and ADW (B) are for storage/analytics, Data Science (C) is for ML—not datasets—only Open Data (D) fits.

Oracle Cloud Infrastructure Open Data Documentation, "Overview".

Detailed Answer in Step-by-Step Solution:

Objective: Understand the effect of False Alarm Probability (FAP) in OCI Anomaly Detection.

Understand FAP: Controls false positive rate—threshold for anomaly flagging.

Evaluate Options:

A: Disable reporting—Incorrect; FAP sets sensitivity, not on/off.

B: Changes sensitivity—Correct; lower FAP = fewer false positives—correct.

C: Count-based error—Incorrect; not a counter.

D: Score per signal—Incorrect; FAP is a global setting.

Reasoning: FAP adjusts detection threshold—direct impact on sensitivity.

Conclusion: B is correct.

OCI documentation states: “False Alarm Probability (FAP) (B) adjusts the model’s sensitivity in Anomaly Detection—lower values increase specificity, reducing false positives.” A, C, and D misinterpret FAP’s role—only B aligns with OCI’s anomaly detection tuning.

Oracle Cloud Infrastructure Anomaly Detection Documentation, "FAP Settings".

Detailed Answer in Step-by-Step Solution:

Objective: Sequence steps for PySpark app development.

Steps:

Launch notebook: First—sets up environment.

Install PySpark conda: Second—adds Spark libraries.

Configure core-site.xml: Third—connects to data.

Develop app: Fourth—writes code.

Data Flow: Fifth—scales (optional).

Evaluate: D (1, 2, 3, 4, 5) matches this logical order.

Reasoning: Notebook first, then setup and coding.

Conclusion: D is correct.

OCI documentation states: “1) Launch a notebook session, 2) install a PySpark conda env, 3) configure core-site.xml, 4) develop your PySpark app, 5) optionally use Data Flow (D).” Other orders (A, B, C) misplace notebook launch or config—D is correct.

Oracle Cloud Infrastructure Data Science Documentation, "PySpark Development".

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:

Objective: Identify three required params for an OCI Data Flow app config.

Understand Data Flow: Runs Spark apps; needs compartment, storage, and identity.

Evaluate Options:

A: Archive path—Optional if script is in Object Storage—incorrect.

B: Local script path—Not needed; script is uploaded—incorrect.

C: Compartment—Required for resource scope—correct.

D: Bucket—Required for script storage/access—correct.

E: Display name—Required for app identification—correct.

Reasoning: C, D, E are mandatory metadata for Data Flow creation—script location is specified via bucket.

Conclusion: C, D, E are correct.

OCI documentation states: “To create a Data Flow application, configure the compartment OCID (C), Object Storage bucket for the PySpark script (D), and a display name (E) in the application object.” Local paths (B) or archives (A) are optional or handled separately—only C, D, E are required per OCI’s Data Flow API spec.

Oracle Cloud Infrastructure Data Flow Documentation, "Creating Applications".