1z0-1110-25 Oracle Cloud Infrastructure 2025 Data Science Professional Questions and Answers

Detailed Answer in Step-by-Step Solution:

Understand OCI IAM Policies: Policies control access using verbs like “inspect,” “read,” “use,” and “manage.”

Define Requirement: Consultants need view-only access without modification rights.

Evaluate Verbs:

A. Use: Allows interaction (e.g., running jobs)—too permissive.

B. Inspect: Grants view-only access to resource details—matches requirement.

C. Manage: Full control (create, update, delete)—too permissive.

D. Read: Includes viewing content (e.g., data), not just metadata—slightly broader than needed.

Conclusion: “Inspect” (B) is the precise verb for view-only access to resource details.

In OCI Identity and Access Management (IAM), the “inspect” verb allows listing and viewing resource metadata without granting modification or data access rights, ideal for this scenario. This is confirmed in the IAM policy reference. (Reference: Oracle Cloud Infrastructure Documentation, "IAM Policy Verbs").

Detailed Answer in Step-by-Step Solution:

Objective: Identify the required configuration for OCI Logging Analytics to collect logs from an instance.

Understand Logging Analytics: Collects and analyzes logs from OCI resources via Management Agents.

Key Concepts:

Entity: Represents the instance (e.g., Linux VM).

Source: Defines log locations (e.g., file paths).

Log Group: Organizes logs for analysis.

Evaluate Options:

A: Log-Log Group—Groups logs, not collection setup.

B: Entity-Log—Links instance to logs, but not source-specific.

C: Source-Entity—Maps log sources to the instance—correct.

D: Log Group-Source—Post-collection organization, not ingestion.

Reasoning: C establishes the link between the instance and its log sources—key for ingestion.

Conclusion: C is correct.

OCI documentation states: “To collect logs using Logging Analytics, configure a Source-Entity Association (C) to link the Management Agent on the instance (entity) to specific log sources (e.g., file paths).” A and D organize logs post-collection, B is less specific—only C is required for ingestion per OCI’s Logging Analytics setup.

Oracle Cloud Infrastructure Logging Analytics Documentation, "Configuring Log Collection".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the WAF component that controls request actions based on criteria.

Understand WAF Components:

Protection Rules: Define conditions and actions (e.g., allow, block, log).

Bot Management: Handles bot traffic, not general request rules.

Origin: Backend server endpoint, not rule-based.

WAF Policy: Umbrella config, but rules specify actions.

Evaluate Options:

A: Protection rules—Set specific criteria and actions—correct.

B: Bot Management—Bot-specific, not general requests.

C: Origin—Defines source, not actions.

D: WAF policy—Broad config, not the granular rules.

Reasoning: Protection rules directly manage request behavior—fit the requirement.

Conclusion: A is correct.

OCI documentation states: “Protection rules (A) in WAF define conditions (e.g., IP, URL) and actions (allow, block, log) for incoming requests.” Bot Management (B) targets bots, Origin (C) is a target server, and WAF Policy (D) encompasses rules but isn’t the action specifier—only A aligns with OCI’s WAF configuration.

Oracle Cloud Infrastructure WAF Documentation, "Protection Rules".

Detailed Answer in Step-by-Step Solution:

Objective: Match a cache rule criterion for exact URL path and query.

Understand Cache Rules: Used in OCI (e.g., WAF, CDN) to cache content.

Evaluate Options:

A: Contains—Partial match, not exact.

B: Is—Exact match of full URL (path + query)—correct.

C: Ends with—Matches end, not full URL.

D: Starts with—Matches start, not full URL.

Reasoning: “URL_IS” checks exact equality—fits requirement.

Conclusion: B is correct.

OCI documentation states: “The URL_IS (B) criterion in cache rules matches when the full URL (path and query) exactly equals the specified value.” A, C, and D are partial matches—only B ensures identical concatenation per OCI’s caching config.

Oracle Cloud Infrastructure WAF Documentation, "Cache Rules Criteria".

Detailed Answer in Step-by-Step Solution:

Objective: Apply all recommended transformations from get_recommendations() in ADS.

Understand ADS Tools: get_recommendations() suggests fixes (e.g., missing values).

Evaluate Options:

A: Returns transformed data—Not for applying—incorrect.

B: Sklearn-style, not ADS-specific—incorrect.

C: auto_transform()—Applies all recommendations—correct.

D: Visualizes, doesn’t apply—incorrect.

Reasoning: auto_transform() executes the fixes suggested by get_recommendations().

Conclusion: C is correct.

OCI documentation states: “After get_recommendations() identifies issues, use auto_transform() (C) on the ADSDataset to apply all recommended transformations at once.” A retrieves, B is external, D visualizes—only C aligns with OCI’s ADS transformation workflow.

Oracle Cloud Infrastructure ADS SDK Documentation, "Data Transformation Methods".

Detailed Answer in Step-by-Step Solution:

Objective: Determine minimum log storage duration before archiving in Logging Analytics.

Understand Logging Analytics: Logs are active before archival.

Evaluate Options:

A: 60 days—Too long for minimum.

B: 10 days—Too short.

C: 30 days—Standard minimum—correct.

D: 15 days—Not OCI’s default.

Reasoning: 30 days is OCI’s documented minimum active period.

Conclusion: C is correct.

OCI documentation states: “Logs in Logging Analytics remain active for a minimum of 30 days (C) before archiving, ensuring availability for analysis.” B and D are shorter, A is longer—only C matches OCI’s policy.

Oracle Cloud Infrastructure Logging Analytics Documentation, "Log Retention".

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:

Understand Published Conda Environments: In OCI Data Science, these are custom conda environments shared across users via Object Storage.

Evaluate Options:

A: Vague—All conda environments can address use cases; not unique to “published.”

B: Incorrect—Availability on reactivation applies to session persistence, not publishing.

C: Correct—Publishing saves the environment to Object Storage for sharing/reuse.

D: Incorrect—Block volumes store session data, not published environments.

Reasoning: The unique aspect of “published” environments is their storage in Object Storage (via odsc conda publish), enabling team access.

Conclusion: C is the distinctive feature.

The OCI Data Science documentation highlights that “published conda environments are saved to an OCI Object Storage Bucket, allowing them to be shared across notebook sessions and users.” This distinguishes C from A (generic), B (session-related), and D (block volume is for session state, not publishing). Publishing to Object Storage is the defining trait per Oracle’s design.

Oracle Cloud Infrastructure Data Science Documentation, "Managing Conda Environments - Publishing" section.

Detailed Answer in Step-by-Step Solution:

Objective: Identify which activity isn’t part of the ML lifecycle.

Define ML Lifecycle: Includes data access, preparation, modeling, evaluation, deployment, and monitoring.

Evaluate Options:

A: Database Management (e.g., DBA tasks) is IT-related, not specific to ML workflows.

B: Model Deployment (e.g., serving predictions) is a key ML phase—correctly included.

C: Modeling (e.g., training) is the core of ML—correctly included.

D: Data Access (e.g., retrieving data) is the first ML step—correctly included.

Reasoning: Database management supports infrastructure, not the ML process directly.

Conclusion: A is the outlier.

The OCI Data Science lifecycle includes “data access, exploration, feature engineering, modeling, deployment, and monitoring,” per the documentation. Database Management (A) is a general ITtask (e.g., optimizing Oracle DB), not an ML-specific activity, unlike B, C, and D, which are integral to OCI’s ML pipeline.

Oracle Cloud Infrastructure Data Science Documentation, "Machine Learning Lifecycle Overview".

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: 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: Identify ADS class for accessing datasets (e.g., scikit-learn).

Evaluate Options:

A: DatasetBrowser—Not an ADS class.

B: DatasetFactory—Loads datasets from sources like scikit-learn—correct.

C: ADSTuner—Hyperparameter tuning, not data access.

D: SecretKeeper—Manages credentials, not datasets.

Reasoning: DatasetFactory simplifies dataset loading (e.g., DatasetFactory.open()).

Conclusion: B is correct.

OCI documentation states: “DatasetFactory in ADS SDK provides methods to easily load datasets from libraries like scikit-learn or other sources (e.g., DatasetFactory.open('sklearn.datasets:load_iris')).” A isn’t real, C tunes models, and D handles secrets—only B fits.

Oracle Cloud Infrastructure ADS SDK Documentation, "DatasetFactory".

Detailed Answer in Step-by-Step Solution:

Prepare Model: Build and train the time series model using historical data.

Verify: Validate the model’s accuracy (e.g., using metrics like MAE or RMSE).

Save: Store the trained model (e.g., in the OCI Model Catalog).

Deploy: Make the model available for predictions (e.g., via OCI Model Deployment).

Predict: Generate revenue forecasts for the upcoming quarter.

Evaluate Options: D follows this logical flow; others (e.g., A starts with “verify” before preparation) don’t.

In OCI Data Science, the workflow for time series forecasting involves preparing the model (training), verifying its performance, saving it to the catalog, deploying it, and then predicting. This sequence is standard for ML deployment in OCI, as per the documentation. (Reference: Oracle Cloud Infrastructure Data Science Documentation, "Time Series Forecasting Workflow").

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:

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: 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: Sequence OCI AutoML pipeline stages.

Stages:

Adaptive sampling: Reduces data size if large.

Feature selection: Picks relevant features.

Algorithm selection: Chooses best model type.

Hyperparameter tuning: Optimizes model params.

Evaluate: C (sampling, features, algorithms, tuning) matches logical flow—data first, then model.

Reasoning: Sampling precedes feature work—standard in OCI.

Conclusion: C is correct.

OCI documentation states: “AutoML pipeline runs 1) adaptive sampling, 2) feature selection, 3) algorithm selection, 4) hyperparameter tuning (C).” Sampling reduces data first, then features and models are optimized—other orders (A, B, D) misalign with OCI’s sequence.

Oracle Cloud Infrastructure AutoML Documentation, "Pipeline Sequence".

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 OCI Secrets: Secrets are sensitive data (e.g., API keys, passwords) managed securely in OCI.

Evaluate Options:

A: Object Storage is for general data, not secure secret management.

B: Vault is OCI’s service for storing and managing secrets securely.

C: Autonomous Data Warehouse is for analytics, not secret storage.

D: Oracle Databases store data, not OCI-specific secrets.

Reasoning: Vault is purpose-built for secrets with encryption and access control.

Conclusion: B is correct.

OCI Vault “provides a secure, centralized service to store and manage secrets, such as passwords and keys, with encryption at rest and fine-grained access policies.” Object Storage (A), Autonomous Data Warehouse (C), and Oracle Databases (D) serve other purposes—only Vault (B) is designed for secrets per OCI’s security architecture.

Oracle Cloud Infrastructure Vault Documentation, "Secrets Management".

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: Locate artifacts for ADS model deployment.

Understand ADS Deployment: Requires model artifacts (e.g., score.py) stored in OCI.

Evaluate Options:

A: Vault—Stores secrets, not models.

B: Depository—Not an OCI term.

C: Model Catalog—Stores models/artifacts for deployment—correct.

D: Artifactory—Not an OCI service.

Reasoning: Model Catalog is OCI’s model repository for ADS.

Conclusion: C is correct.

OCI documentation states: “ADS SDK deploys models from the Model Catalog, where trainedmodels and artifacts (e.g., score.py) are stored.” Vault (A) is for secrets, B and D aren’t real—only C supports ADS deployment.

Oracle Cloud Infrastructure Data Science Documentation, "ADS Model Deployment".

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: Identify the file system type for OCI File Storage.

Understand File Storage: Network-attached storage in OCI.

Evaluate Options:

A: NFSv3—Network File System, used by File Storage—correct.

B: iSCSI—Block storage protocol, not File Storage.

C: Paravirtualized—Virtualization mode, not file system.

D: NVMe SSD—Hardware, not file system.

Reasoning: NFSv3 is OCI File Storage’s protocol.

Conclusion: A is correct.

OCI documentation states: “File Storage uses NFSv3 (A) as its file system protocol, providing shared storage across instances.” B, C, and D are unrelated—only A aligns with OCI’s File Storage design.

Oracle Cloud Infrastructure File Storage Documentation, "File System Protocol".

Detailed Answer in Step-by-Step Solution:

Objective: Differentiate data scientist vs. data engineer roles.

Define Roles:

Data Engineer: Builds pipelines, prepares data.

Data Scientist: Analyzes data, builds models.

Evaluate Options:

A: Engineer preps, scientist analyzes—Correct division.

B: Reverses roles—Incorrect.

C: Overlaps roles—Scientist doesn’t typically build pipelines.

D: Misaligns—Analyst isn’t the focus.

Reasoning: A reflects standard role separation.

Conclusion: A is correct.

OCI documentation notes: “Data engineers focus on collecting and preparing data through pipelines, while data scientists analyze it to derive insights and build models.” A aligns, B inverts, C overcomplicates, and D shifts focus—only A is accurate.

Oracle Cloud Infrastructure Data Science Documentation, "Roles in Data Science".

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:

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: 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: 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:

Data Access: The first step in any machine learning workflow is accessing the raw data. This involves retrieving the user commute data collected over the past 3 years from the bike-sharing platform’s storage system.

Data Exploration: Once data is accessed, it’s explored to understand its structure, quality, and patterns (e.g., missing values, distributions). This step helps identify what preprocessing is needed.

Feature Engineering: After understanding the data, features are created or transformed (e.g., commute duration, time of day) to improve model performance. This step precedes feature exploration because you need engineered features to analyze further.

Feature Exploration: This involves analyzing the engineered features (e.g., correlation analysis, importance ranking) to refine them or select the most relevant ones for modeling.

Modeling: Finally, the prepared data and features are used to train and evaluate a machine learning model.

Option C (Data Access, Data Exploration, Feature Engineering, Feature Exploration, Modeling) follows this logical sequence, aligning with standard ML workflows.

The correct order reflects the machine learning lifecycle as outlined in Oracle’s OCI Data Science documentation. Data Access is the initial step to retrieve data, followed by Data Exploration to assess it (e.g., using OCI Data Science Notebook Sessions with tools like pandas). Feature Engineering transforms raw data into meaningful inputs, followed by Feature Exploration to analyze feature importance (e.g., using ADS SDK’s correlation tools). Modeling is the final step where the model is built and trained. This sequence is consistent with Oracle’s recommended practices for building ML models in OCI Data Science (Reference: Oracle Cloud Infrastructure Data Science Service Documentation, "Machine Learning Lifecycle").

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.

Detailed Answer in Step-by-Step Solution:

Objective: Select two metrics for multiclass classification in AutoML.

Understand Multiclass Metrics: Focus on class-specific performance—classification, not regression.

Evaluate Options:

A. Recall: Measures true positives per class—key for multiclass—correct.

B. Mean squared error: Regression metric—incorrect.

C. F1 Score: Balances precision and recall—standard for multiclass—correct.

D. R-Squared: Regression fit—incorrect.

E. Explained variance: Regression metric—incorrect.

Reasoning: A and C assess classification accuracy across multiple classes—fit AutoML’s evaluation.

Conclusion: A and C are correct.

OCI AutoML documentation states: “For multiclass classification, common evaluation metrics include recall (A) for per-class sensitivity and F1 Score (C) for balanced performance.” B, D, and E are regression-focused—only A and C are supported and relevant per OCI’s AutoML metrics suite.

Oracle Cloud Infrastructure AutoML Documentation, "Evaluation Metrics for Classification".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the invalid MFA statement.

Evaluate Options:

A: True—Users can’t disable MFA; admin-controlled.

B: False—Multiple devices can be registered—invalid.

C: True—Authenticator app is required.

D: True—Admins can disable MFA.

Reasoning: B contradicts OCI’s multi-device support.

Conclusion: B is incorrect.

OCI documentation states: “Users can register multiple devices for MFA (B is false), must use an authenticator app (C), and cannot disable MFA themselves (A)—admins can (D).” Only B is not valid per OCI’s IAM MFA policy.

Oracle Cloud Infrastructure IAM Documentation, "Multi-Factor Authentication".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the OCI Data Science interaction method that doesn’t require scripting.

Understand Interaction Methods: OCI provides multiple ways to interact with Data Science services—some are GUI-based, others script-based.

Evaluate Options:

A. OCI Console: A web-based graphical interface allowing users to manage resources (e.g., create notebook sessions, deploy models) via point-and-click—no scripting needed.

B. CLI: Command Line Interface requires writing commands (scripts) to execute tasks (e.g., oci data-science notebook-session create).

C. Language SDKs: Software Development Kits (e.g., Python SDK) require coding to interact programmatically (e.g., oci.data_science.DataScienceClient).

D. REST APIs: Application Programming Interfaces require scripted HTTP requests (e.g., using curl or a programming language).

Reasoning: Only the OCI Console (A) offers a no-code, user-friendly interface, while B, C, and D rely on scripting or programming.

Conclusion: A is the correct answer as it eliminates the need for scripting.

The OCI Console is described in the documentation as “a browser-based interface that allows users to manage OCI Data Science resources, such as creating notebook sessions or jobs, without writing code or scripts.” In contrast, the CLI (B) requires command-line scripts, SDKs (C) need programming (e.g., Python), and REST APIs (D) involve scripted API calls. The Console’s GUI distinguishes it as the only option functioning without scripting, aligning with Oracle’s design for accessibility to non-programmers.

Oracle Cloud Infrastructure Data Science Documentation, "Getting Started with OCI Console" section.

Detailed Answer in Step-by-Step Solution:

Objective: Get summary info from an ADSDataset object.

Evaluate Options:

A: Correlation matrix—Specific, not full summary.

B: Converts to XGBoost—Not for summary.

C: Executes computation—Not summary-focused.

D: Displays summary (types, counts, dist)—correct.

Reasoning: show_in_notebook() provides a comprehensive overview.

Conclusion: D is correct.

OCI documentation states: “show_in_notebook() (D) from ADSDataset displays a summary of the dataset, including feature types, observation count, and distributions, in a notebook.” A is partial, B and C are unrelated—only D meets the need per ADS SDK.

Oracle Cloud Infrastructure ADS SDK Documentation, "ADSDataset Methods".

Detailed Answer in Step-by-Step Solution:

Objective: Identify IAM components in OCI.

Understand IAM: Manages access via policies, groups, etc.

Evaluate Options:

A: Policies—Core IAM component—correct.

B: Subnets—Networking, not IAM.

C: Instances—Compute, not IAM.

D: VCN—Networking, not IAM.

Reasoning: Only A is an IAM element—others are resources.

Conclusion: A is correct.

OCI documentation states: “IAM includes components like policies (A), groups, and compartments to control resource access.” B, C, and D are infrastructure, not IAM—only A fits per OCI’s IAM framework.

Oracle Cloud Infrastructure IAM Documentation, "IAM Components".

Detailed Answer in Step-by-Step Solution:

Objective: Troubleshoot a 404 auth error when saving a model with resource principal.

Understand Resource Principal: Allows notebook sessions to act as principals via dynamic groups and policies—no user credentials.

Analyze 404 Error: Indicates permission failure—likely IAM misconfiguration.

Evaluate Options:

A: Block volume storage—Irrelevant to auth; it’s about saving locally—incorrect.

B: Dynamic group matching—Ensures notebook is recognized—correct.

C: User group policy—Not used with resource principal—incorrect.

D: Dynamic group policy—Grants catalog access—correct.

E: Service Gateway—Network-related, not auth-specific—incorrect.

Reasoning: Resource principal needs B (group inclusion) and D (policy perms)—404 points to these.

Conclusion: B and D are correct.

OCI documentation states: “For ADS SDK to save to the Model Catalog using resource principal, ensure (1) a dynamic group includes notebook sessions with matching rules (e.g., resource.type ='datasciencenotebooksession') (B), and (2) a policy grants manage data-science-models to that dynamic group (D).” A is storage, C is user-based, E is network—only B and D fix the auth issue per OCI’s IAM setup.

Oracle Cloud Infrastructure Data Science Documentation, "Resource Principal with Model Catalog".

Detailed Answer in Step-by-Step Solution:

Objective: Determine which validator handler runs for is_tech_job(job_family='Engineering').

Understand Validator System: Likely ADS SDK—executes handlers based on conditions.

Analyze Validators:

Default: is_tech_job_default_handler—No condition, fallback.

Open: is_tech_job_open_handler—Condition ('job_family',)—requires job_family arg.

Closed: is_tech_job_closed_handler—Condition ('job_family': 'IT')—requires job_family='IT'.

Evaluate Call: job_family='Engineering'—Matches job_family presence, not IT.

Reasoning:

Open handler applies (tuple condition means arg exists).

Closed fails (Engineering ≠ IT).

Default is overridden by specific matches.

Conclusion: D is correct.

OCI ADS documentation states: “Validators execute the most specific handler matching the condition; for is_tech_job(job_family='Engineering'), is_tech_job_open_handler (D) runs as it matches job_family presence, while is_tech_job_closed_handler (C) requires IT—default (A) is bypassed, no error (B).” Only D fits per ADS validator logic.

Oracle Cloud Infrastructure ADS SDK Documentation, "Feature Type Validators".

Detailed Answer in Step-by-Step Solution:

Objective: Identify top languages for data science.

Evaluate Options:

A: C/C++—Low-level, less common for data tasks.

B: Python (ML, libraries), R (stats), SQL (data)—Industry standards.

C: Java (enterprise), JavaScript (web)—Not data-focused.

Reasoning: B aligns with data science tools (e.g., pandas, ggplot).

Conclusion: B is correct.

OCI documentation highlights “Python, R, and SQL as the most widely used languages in Data Science for modeling, analysis, and data querying.” C/C++ (A) and Java/JS (C) are less prevalent—B matches OCI’s notebook support and industry trends.

Oracle Cloud Infrastructure Data Science Documentation, "Supported Languages".

Detailed Answer in Step-by-Step Solution:

Objective: Identify supported annotation classes in OCI Data Labeling.

Understand Tool: Supports image/text annotations for ML.

Evaluate Options:

A: Object detection—Yes (bounding boxes).

B: Named entity—Text-specific, not primary for images.

C: Classification—Yes (labels for images/text).

D: Key-point—Not listed in OCI docs.

E: Polygonal—Not explicitly supported.

F: Semantic segmentation—Yes (pixel-level).

Reasoning: A, C, F match OCI’s image/text focus.

Conclusion: A, C, F are correct.

OCI Data Labeling supports “object detection (A), classification (C), and semantic segmentation (F) for images and text,” per documentation. B is text-specific, D and E aren’t highlighted—only A, C, F are core classes.

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

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: 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: 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: Select an OCI AI service to sort images by language.

Evaluate Options:

A: Digital Assistant—Chatbots, not image/language processing.

B: Vision—Image analysis (e.g., object detection), not language sorting.

C: Speech—Audio-to-text, not image-based.

D: Language—Text analysis (e.g., language detection) after OCR—correct.

Reasoning: Images need OCR (Vision) then language detection (Language)—D fits the sorting task.

Conclusion: D is correct.

OCI Language “detects and classifies languages in text,” often paired with OCI Vision’s OCR to process document images. Vision (B) extracts text, but Language (D) sorts by language—Digital Assistant (A) and Speech (C) don’t apply. Documentation supports this workflow.

Oracle Cloud Infrastructure Language Documentation, "Language Detection".

Detailed Answer in Step-by-Step Solution:

Objective: Identify ADS class for dataset access (e.g., scikit-learn).

Evaluate Options:

A: DataLabeling—Not an ADS class.

B: DatasetBrowser—Not real.

C: SecretKeeper—Credentials, not data.

D: DatasetFactory—Loads datasets (e.g., open())—correct.

Reasoning: DatasetFactory simplifies library dataset access.

Conclusion: D is correct.

OCI documentation states: “DatasetFactory (D) in ADS SDK accesses datasets from libraries like scikit-learn (e.g., DatasetFactory.open('sklearn.datasets:load_iris')).” A, B, and C don’t exist or apply—only D fits.

Oracle Cloud Infrastructure ADS SDK Documentation, "DatasetFactory".