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

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:

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:

Objective: Visualize correlation between continuous and categorical features using ADS SDK.

Understand Correlation Types:

Continuous vs. Continuous: Pearson correlation.

Categorical vs. Categorical: Cramer’s V.

Continuous vs. Categorical: Correlation ratio (eta).

Evaluate Options:

A. corr(): General correlation (Pearson), not suited for mixed types—incorrect.

B. correlation_ratio_plot(): Plots correlation ratio for continuous-categorical—correct.

C. pearson_plot(): Not an ADS method; Pearson is continuous-only—incorrect.

D. cramersv_plot(): Cramer’s V for categorical-categorical—incorrect.

Reasoning: Correlation ratio measures association between continuous and categorical variables—ideal for heatmap in this mixed scenario.

Conclusion: B is correct.

OCI documentation states: “The correlation_ratio_plot() method (B) in ADS SDK generates a heatmap displaying the correlation ratio between continuous and categorical features, suitable for identifying highly correlated features for removal.” corr() (A) defaults to Pearson, pearson_plot() (C) isn’t real, and cramersv_plot() (D) is for categorical pairs—only B aligns with OCI’s ADS capabilities for this use case.

Oracle Cloud Infrastructure ADS SDK Documentation, "Correlation Visualization Methods".

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 the firewall type protecting against web app attacks like SQL injection and XSS.

Understand Firewall Types:

Stateful Inspection: Tracks connection states, not app-specific.

Web Application Firewall (WAF): Targets web app vulnerabilities.

Incident Firewall: Not a recognized term.

Packet Filtering: Basic packet rules, not app-aware.

Evaluate Options:

A: Stateful—General network, not web-specific—incorrect.

B: WAF—Designed for SQLi, XSS—correct.

C: Incident—Non-existent—incorrect.

D: Packet—Low-level, not app-focused—incorrect.

Reasoning: WAF specializes in web app security—matches requirement.

Conclusion: B is correct.

OCI documentation states: “Web Application Firewall (WAF) (B) protects against web application attacks like SQL injection and cross-site scripting by inspecting HTTP traffic.” A and D handle network-level threats, C isn’t real—only B aligns with OCI’s WAF purpose.

Oracle Cloud Infrastructure WAF Documentation, "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: 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 protection for data at rest/transit with customer control.

Evaluate Options:

A: Controls—Broad, not specific to encryption.

B: Isolation—Separates tenants, not crypto-focused.

C: Encryption—Secures data, allows key management—correct.

D: Federation—Auth sharing, not data protection.

Reasoning: C provides crypto control (e.g., Vault keys).

Conclusion: C is correct.

OCI documentation states: “Data encryption (C) protects data at rest and in transit, with customer-managed keys in OCI Vault meeting compliance needs.” A and B are broader, D is unrelated—only C fits per OCI’s security model.

Oracle Cloud Infrastructure Security Documentation, "Data Encryption".

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: 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 Language AI capabilities.

Understand OCI Language: Focuses on text analysis tasks.

Evaluate Options:

A: Table extraction—Vision, not Language—incorrect.

B: Punctuation correction—Not offered—incorrect.

C: Sentence diagramming—Not supported—incorrect.

D: Topic classification—Supported (custom/pretrained)—correct.

E: Sentiment analysis—Supported (pretrained)—correct.

Reasoning: D and E are core text analysis features of OCI Language.

Conclusion: D and E are correct.

OCI documentation states: “OCI Language offers topic classification (D) and sentiment analysis (E) for text analysis, among other features.” A belongs to Vision, B and C aren’t available—only D and E match OCI Language’s capabilities.

Oracle Cloud Infrastructure Language Documentation, "Text Analysis Features".

Detailed Answer in Step-by-Step Solution:

Objective: Fix network timeout for pip install in a notebook.

Evaluate Options:

A: FastConnect—On-premises link, not public internet.

B: VNIC—Default, not the issue.

C: NAT Gateway—Grants internet access—correct.

D: Service Gateway—OCI services, not PyPI.

Reasoning: C enables outbound traffic to public repos.

Conclusion: C is correct.

OCI documentation states: “A NAT Gateway (C) is required for notebook sessions in private subnets to access public internet repositories like PyPI.” A, B, and D don’t provide this—only C resolves the timeout.

Oracle Cloud Infrastructure Data Science Documentation, "Notebook Networking".

Detailed Answer in Step-by-Step Solution:

Objective: Sequence steps for a PySpark app in OCI Data Science.

Evaluate Steps:

Launch notebook: First—provides the environment.

Install PySpark conda: Second—sets up Spark libraries.

Configure core-site.xml: Third—connects to data (e.g., Object Storage).

Develop app: Fourth—writes the PySpark code.

Data Flow: Fifth—optional scaling, post-development.

Check Options: D (1, 2, 3, 4, 5) matches this logical flow.

Reasoning: Notebook first, then setup, coding, and scaling.

Conclusion: D is correct.

OCI documentation recommends: “1) Launch a notebook session, 2) install a PySpark conda environment, 3) configure core-site.xml for data access, 4) develop your PySpark application, and 5) optionally use Data Flow for scale.” D follows this—others (A, B, C) misorder critical steps like launching the notebook.

Oracle Cloud Infrastructure Data Science Documentation, "PySpark in Notebooks".

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 the initial data science step.

Define Process: Starts with problem definition, then data and modeling.

Evaluate Options:

A: Data collection—Second step after problem definition.

B: Modeling—Later stage.

C: Hypothesis—Sets the goal, first step—correct.

D: Data owners—Collaboration, not the start.

Reasoning: Hypothesis drives the process (e.g., “Can we predict churn?”).

Conclusion: C is correct.

OCI documentation states: “The data science process begins with defining an analytical hypothesis to address a business problem, followed by data collection and analysis.” C precedes A, B, and D—aligning with OCI’s structured approach.

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

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:

Context Analysis: You need to investigate an existing deep neural network model in the OCI Model Catalog with no prior information.

Understand Model Catalog: The Model Catalog stores trained models along with metadata, hyperparameters, and provenance (origin and history) details.

Evaluate Options:

A. Refer to the code inside the model: The model artifact (e.g., a serialized file like .pkl) doesn’t typically include readable source code; it’s a trained object, not the training script.

B. Check for model taxonomy details: Taxonomy (e.g., classification vs. regression) provides high-level categorization but lacks specifics like framework or architecture.

C. Check for metadata tags: Metadata includes name, description, and tags, offering some context but not detailed framework info (e.g., TensorFlow vs. PyTorch).

D. Check for provenance details: Provenance tracks the model’s creation process, including the framework, training environment, and data sources, providing the most comprehensive insight.

Reasoning: Provenance details are designed to document the “how” and “what” of model creation, making them ideal for uncovering the framework (e.g., Keras, PyTorch) and other specifics absent from initial handover.

Conclusion: D is the best approach for detailed investigation.

In OCI Data Science, the Model Catalog stores provenance information, which includes “details about the model’s origin, such as the framework used (e.g., TensorFlow, PyTorch), the training environment, and dataset references.” This is more informative than metadata tags (C), which are user-defined and less structured, or taxonomy (B), which is broad. The model artifact (A) is a binary file (e.g., pickle), not a readable codebase. Provenance (D) offers a detailed audit trail, critical for analyzing an undocumented deep neural network model like this one.

Oracle Cloud Infrastructure Data Science Documentation, "Model Catalog - Provenance Details" section.

Detailed Answer in Step-by-Step Solution:

Define Resource Principals: They allow OCI resources (e.g., notebook sessions) to authenticate to other OCI services without user credentials.

Evaluate Options:

A: False—Resource principals eliminate manual credential management.

B: False—They’re secure, leveraging IAM policies, not less secure than API keys.

C: False—Data Science supports resource principals for accessing resources (e.g., Object Storage).

D: True—Resource principals are an IAM feature authorizing resources as actors.

Reasoning: D captures the essence of resource principals as an IAM mechanism.

Conclusion: D is correct.

OCI documentation states: “A resource principal is an IAM feature that enables OCI resources, such as compute instances or notebook sessions, to act as principal actors and authenticate to other OCI services using policies.” This refutes A (no credentials needed), B (secure method), and C (supported in Data Science), making D the accurate statement.

Oracle Cloud Infrastructure IAM Documentation, "Resource Principals".

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: Address declining prediction accuracy and verify model performance.

Analyze Problem: Degradation over time suggests data drift or model staleness—common ML issues.

Evaluate Options:

A. Retrain the model: Uses new data to update the model—fixes accuracy—correct.

B. Validate with recent data: Tests performance but doesn’t fix—diagnostic only.

C. Drift monitoring: Detects data distribution shifts—verifies cause—correct.

D. Redeploy the model: Repeats deployment, doesn’t address root cause.

E. Operational monitoring: Tracks infra (e.g., latency), not prediction accuracy.

Reasoning: C identifies drift (why accuracy dropped), A corrects it—best pair for verification and improvement.

Conclusion: A and C are correct.

OCI documentation states: “Drift monitoring (C) detects changes in data distribution that impact accuracy, while retraining (A) with new data restores model performance.” Validation (B) checks but doesn’t fix, redeployment (D) is redundant, and operational monitoring (E) is infra-focused—only A and C align with OCI’s model maintenance strategy.

Oracle Cloud Infrastructure Data Science Documentation, "Model Monitoring and Retraining".

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 a step unique to MLOps vs. DevOps.

Compare MLOps and DevOps:

DevOps: Focuses on software deployment (CI/CD).

MLOps: Extends DevOps to ML, adding model-specific steps.

Evaluate Options:

A: Continuous deployment—Common to both (software/models).

B: Continuous integration—Common to both (code merging).

C: Continuous delivery—Common to both (releasing updates).

D: Continuous training—Unique to MLOps (retraining models with new data).

Reasoning: Only D addresses ML-specific needs (model retraining).

Conclusion: D is correct.

OCI documentation notes: “MLOps extends DevOps with continuous training, a process unique to machine learning where models are retrained with new data to maintain performance.” CI (B), CD (A), and delivery (C) are shared with DevOps—only continuous training (D) is MLOps-specific.

Oracle Cloud Infrastructure Data Science Documentation, "MLOps Concepts".

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: Select an auth method for third-party APIs lacking OCI signature support.

Understand OCI Auth: Typically uses API keys, but alternatives exist for non-standard APIs.

Evaluate Options:

A: Username/password—Not API-friendly, insecure.

B: API Signing Key—Requires signature-based auth, unsupported here.

C: SSH Key—For instance access, not APIs.

D: Auth Token—Simple token for API calls—correct.

Reasoning: Auth Token provides a bearer token for APIs without signature complexity.

Conclusion: D is correct.

OCI documentation states: “For third-party APIs not supporting signature-based authentication, use an Auth Token (D), a secure, revocable token for accessing OCI resources via REST APIs.” A, B, and C don’t fit non-signature scenarios—only D ensures compatibility per OCI’s IAM options.

Oracle Cloud Infrastructure IAM Documentation, "Auth Tokens for API Access".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the non-Observability and Management (O&M) service in OCI.

Understand O&M: Includes monitoring, logging, events tools.

Evaluate Options:

A: Event Services—Triggers actions, part of O&M—correct.

B: OCI Management Service—Not a defined O&M service—incorrect.

C: Logging Analytics—Log analysis, O&M component—correct.

D: Logging—Log collection, O&M component—correct.

Reasoning: B isn’t listed in OCI’s O&M suite—others are.

Conclusion: B is correct (not part of O&M).

OCI documentation lists “Observability and Management Services as including Event Services (A), Logging Analytics (C), and Logging (D)—‘OCI Management Service’ (B) is not a recognized component.” B appears to be a misnomer—only A, C, D are O&M per OCI’s service catalog.

Oracle Cloud Infrastructure Observability and Management Documentation, "Service Overview".

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: 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: 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: 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: Securely authenticate a recurring OCI Job.

Evaluate Options:

A: PAR—Limited duration, insecure for recurring jobs.

B: Resource principal—Secure, managed auth for Jobs—correct.

C: Personal config—Unscalable, security risk.

D: Vault with personal keys—Complex, still uses user creds.

Reasoning: B uses OCI’s native, secure resource principal mechanism.

Conclusion: B is correct.

OCI documentation states: “For Jobs accessing sensitive data, use resource principals with a dynamic group (e.g., resource.type = 'datasciencejobrun') and policies granting access to Object Storage and Model Catalog—secure and scalable.” A is temporary, C and D risk credential exposure—B is best practice.

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

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

Understand Notebook Sessions: These are OCI compute instances running JupyterLab.

Deactivation Impact: Deactivating stops the session to save costs.

Evaluate Options:

A: False—Costs decrease as compute stops.

B: False—Boot volume data isn’t preserved; block volume data is.

C: True—The compute instance shuts down, halting billing.

D: False—Block volume persists unless explicitly deleted.

Reasoning: Deactivation stops the instance (C), preserving block volume data separately.

Conclusion: C is correct.

The OCI documentation states: “When a notebook session is deactivated, the underlying compute instance stops, and billing for compute resources ceases. Data on the attached block volume is preserved, but the boot volume is not.” A is backwards, B misattributes preservation, and D overstates deletion—only C aligns with the process.

Oracle Cloud Infrastructure Data Science Documentation, "Notebook Session Lifecycle".

Detailed Answer in Step-by-Step Solution:

Objective: Locate stdout/stderr output from score.py in deployment.

Understand Deployment: score.py runs in a model endpoint; logs are managed by OCI.

Evaluate Options:

A: False—No VM file is defined by default; logs go to OCI Logging.

B: False—Console displays UI, not raw logs.

C: False—Cloud Shell is a separate tool, not a log destination.

D: True—Predict logs in OCI Logging capture stdout/stderr.

Reasoning: OCI centralizes logs in its Logging service for deployments.

Conclusion: D is correct.

OCI documentation states: “During model deployment, stdout and stderr from score.py are automatically sent to the predict log in the OCI Logging service, as configured in the deployment settings.” A, B, and C don’t align with this managed logging approach—only D is accurate.

Oracle Cloud Infrastructure Data Science Documentation, "Model Deployment - Logging".

Detailed Answer in Step-by-Step Solution:

Objective: Publish a conda env to Object Storage.

Process: Initialize bucket config, then publish env.

Evaluate Options:

A: Publishes env with slug—correct final step.

B: Lists envs—unrelated to publishing.

C: Sets bucket details—required setup—correct.

D: Creates env—not publishing.

E: Activates env—not for sharing.

Reasoning: C sets up, A executes—standard workflow.

Conclusion: A and C are correct.

OCI documentation states: “To publish a conda environment, first run odsc conda init (C) with bucket namespace and name, then odsc conda publish (A) with a slug to upload to Object Storage.” B, D, and E serve other purposes—only A and C are required per OCI’s process.

Oracle Cloud Infrastructure Data Science CLI Reference, "Publishing Conda Environments".

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: 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 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 mechanism for sharing and reloading ML models in OCI Data Science.

Evaluate Options:

A. Model provenance: Tracks model origin—informative but not a sharing mechanism.

B. Model taxonomy: Categorizes models (e.g., regression)—not for sharing/loading.

C. Model deployment: Makes models accessible as endpoints, not for notebook reloading.

D. Model catalog: Stores models and artifacts, enabling sharing and loading into sessions.

Reasoning: The Model Catalog is OCI’s centralized repository for saving, sharing, and retrieving models (e.g., via ADS SDK).

Conclusion: D is the correct tool.

The OCI Model Catalog “enables data scientists to save trained models and their artifacts, share them with team members, and load them back into notebook sessions for further use or evaluation.” Provenance (A) and taxonomy (B) are metadata, while deployment (C) serves inference, not notebook access. D is explicitly designed for this purpose.

Oracle Cloud Infrastructure Data Science Documentation, "Model Catalog Usage".

Detailed Answer in Step-by-Step Solution:

Objective: Identify the non-visualized AutoML stage with small data.

Understand AutoML Pipeline: Includes sampling, feature/algorithm selection, tuning.

Evaluate Options:

A: Feature selection—Visualized (e.g., feature importance).

B: Algorithm selection—Visualized (e.g., algorithm scores).

C: Adaptive sampling—Skipped/visualization absent for <1000 rows.

D: Hyperparameter tuning—Visualized (e.g., trial plots).

Reasoning: Adaptive sampling optimizes large datasets; small data skips it, omitting visuals.

Conclusion: C is correct.

OCI AutoML documentation notes: “Adaptive sampling is applied to large datasets (>1000 rows) to reduce size; for smaller datasets, it’s skipped, and no visualization is generated.” Other stages (A, B,D) produce visuals—only C is absent here.

Oracle Cloud Infrastructure AutoML Documentation, "Pipeline Stages".

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: Find a true statement about ML models.

Evaluate Options:

A: True—Data drift (changes in data distribution) degrades performance over time.

B: False—Static predictions don’t improve without retraining.

C: False—Models need updates as data changes, unlike static software.

D: False—Even high-quality models require retraining with new data.

Reasoning: A reflects the reality of data drift, a common ML challenge.

Conclusion: A is correct.

OCI documentation notes: “Model performance can degrade over time due to data drift, where the underlying data distribution changes, necessitating monitoring and retraining.” B, C, and D contradict this—static predictions don’t improve (B), models aren’t static (C), and retraining is needed (D). A is the accurate aspect.

Oracle Cloud Infrastructure Data Science Documentation, "Model Monitoring and Drift".

Detailed Answer in Step-by-Step Solution:

Objective: Identify three stages in OCI AutoML Pipeline.

Understand Pipeline: Automates ML steps from data to model training.

Evaluate Options:

A: Feature Selection—Selects relevant features—correct.

B: Adaptive Sampling—Reduces data size—correct.

C: Model Deployment—Post-pipeline step—incorrect.

D: Feature Extraction—Not explicit in OCI AutoML—incorrect.

E: Algorithm Selection—Chooses best model—correct.

Reasoning: A, B, E are core automated stages; C and D are separate.

Conclusion: A, B, E are correct.

OCI documentation lists “AutoML Pipeline stages as adaptive sampling (B), feature selection (A), algorithm selection (E), and hyperparameter tuning.” Deployment (C) is post-pipeline, and extraction (D) isn’t highlighted—only A, B, E are included per OCI’s design.

Oracle Cloud Infrastructure AutoML Documentation, "Pipeline Components".

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: Scale up a notebook session without losing work.

Understand Persistence: Block volume stores session data (e.g., /home/datascience).

Evaluate Options:

A: Recreating work—inefficient, risks loss.

B: Local download/upload—cumbersome, unnecessary.

C: Use block volume persistence, scale up—efficient, preserves work—correct.

D: Object Storage—extra steps, not needed with block volume.

Reasoning: C leverages OCI’s built-in persistence for seamless scaling.

Conclusion: C is correct.

OCI documentation states: “Files in /home/datascience are stored on the block volume. To scale up, deactivate the session, provision a new one with a larger shape, and the block volume persists your work.” A loses data, B and D add complexity—only C is optimal.

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

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