1z0-1110-25 Oracle Cloud Infrastructure 2025 Data Science Professional Free Practice Exam Questions (2025 Updated)

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

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: Convert fixed to flexible load balancer in OCI.

Understand Load Balancers: Fixed (e.g., 10 Mbps) vs. flexible (dynamic shapes).

Evaluate Options:

A: False—Conversion possible via recreation.

B: Update Shape—For flexible only, not conversion.

C: Delete and recreate—Standard method—correct.

D: Edit Listener—Configures rules, not type.

Reasoning: OCI requires new creation for type change.

Conclusion: C is correct.

OCI documentation states: “To change from a fixed to a flexible load balancer, delete the existing fixed load balancer and create a new flexible one (C)—direct conversion isn’t supported.” A is too absolute, B and D don’t apply—only C matches OCI’s process.

Oracle Cloud Infrastructure Load Balancing Documentation, "Changing Load Balancer Type".

Detailed Answer in Step-by-Step Solution:

Objective: Optimize embarrassingly parallel workload in OCI Jobs.

Evaluate Options:

A: Sequential runs—Inefficient for parallel tasks.

B: Simultaneous runs—Maximizes parallelism—correct.

C: False—Jobs support parallelism.

D: One job per run—Misstates capability, wasteful.

Reasoning: B leverages OCI’s parallel run support.

Conclusion: B is correct.

OCI documentation states: “For embarrassingly parallel tasks, create one Job and launch multiple simultaneous Job Runs (B) to process data efficiently.” A is slow, C is incorrect, and Dovercomplicates—B is the best approach.

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

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 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: Prevent deployment failure due to high utilization.

Evaluate Options:

A: More instances—Scales capacity—correct.

B: Delete—Stops service, not a solution.

C: Fewer instances—Worsens utilization.

D: Larger VM—Increases resource capacity—correct.

E: Reduce bandwidth—Limits load—correct.

Reasoning: A and D boost capacity, E controls demand—proactive fixes.

Conclusion: A, D, E are correct.

OCI documentation advises: “To handle high utilization, increase instances (A), use a larger compute shape (D), or adjust load balancer bandwidth (E) to manage request volume.” B stops service, C reduces capacity—only A, D, E prevent failure per OCI’s scaling options.

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

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 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: 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: 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: Run a complex Python project as an OCI Job.

Evaluate Options:

A: Auto-identification—False; entrypoint must be set.

B: Rewrite—Unnecessary, inefficient.

C: Auto-executable—False; needs explicit entrypoint.

D: ZIP with entrypoint—Correct, flexible approach.

Reasoning: D preserves structure, specifies execution.

Conclusion: D is correct.

OCI documentation states: “For complex projects, ZIP the folder and upload as a Job artifact, then set JOB_RUN_ENTRYPOINT (D) to the main executable (e.g., main.py).” Auto-detection (A, C) isn’t supported, and B discards structure—D is best.

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

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

Define Git: Git is a version control system—centralized vs. distributed is key.

Evaluate Options:

A: Incorrect—Git is distributed, not centralized (e.g., SVN is centralized).

B: Correct—Distributed, tracks file changes across local and remote repos.

C: Incorrect—Git allows simultaneous contributions; it manages, not prevents, merges.

D: Incorrect—Centralized is wrong, and “copious data” is vague.

Reasoning: Git’s distributed nature (each user has a full repo copy) and change-tracking are core traits.

Conclusion: B is accurate.

OCI documentation aligns with Git’s official definition: “Git is a distributed version control system that tracks changes to files, enabling collaboration and version history management.” A and D misclassify it as centralized, while C misrepresents merge handling—B captures Git’s essence as used in OCI Data Science.

Oracle Cloud Infrastructure Code Repository Documentation, "Git Overview".

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 an OCI AI service for text and table extraction from documents.

Evaluate Options:

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

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

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

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

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

Conclusion: D is correct.

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

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