Detailed Answer in Step-by-Step Solution:
Objective: Identify the key difference between supervised and unsupervised learning.
Define Types:
Supervised: Uses labeled data (e.g., input-output pairs) to predict outcomes.
Unsupervised: Uses unlabeled data to find patterns (e.g., clustering).
Evaluate Options:
A: Labeled vs. unlabeled—Core distinction, correct.
B: Monitoring—Misleading, not the primary difference.
C: Image recognition—False, supervised applies broadly.
D: Data Engineer—Irrelevant to learning type.
Reasoning: A captures the foundational data difference.
Conclusion: A is correct.
OCI documentation states: “Supervised learning uses labeled data to train models for prediction, while unsupervised learning analyzes unlabeled data to discover patterns.” B, C, and D misrepresent this—only A aligns with OCI’s ML definitions and industry standards.
1: Oracle Cloud Infrastructure Data Science Documentation, "Machine Learning Types".

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.
1: Oracle Cloud Infrastructure Data Science Documentation, "Getting Started with OCI Console" section.

Detailed Answer in Step-by-Step Solution:
Objective: Address declining model performance and improve churn prediction.
Analyze Issue: Poor predictions suggest data drift or model staleness—common ML challenges.
Evaluate Options:
A . Drift monitoring: Tracks changes in data distribution—identifies root cause of accuracy drop—correct.
B . Redeploy the model: Repeats deployment without fixing the issue—ineffective alone.
C . Operational monitoring: Tracks system health (e.g., latency), not prediction quality.
D . Retrain the model: Updates model with new data—directly improves accuracy—correct.
E . Validate with recent data: Checks performance but doesn’t fix—diagnostic, not corrective.
Reasoning: A diagnoses drift (cause), D retrains to adapt (solution)—best combo to verify and lower churn.
Conclusion: A and D are correct.
OCI documentation advises: “Drift monitoring (A) detects shifts in data distribution that degrade model performance, while retraining (D) with fresh data restores accuracy.” Redeployment (B) doesn’t address drift, operational monitoring (C) focuses on infra, and validation (E) is a check—not a fix. A and D align with OCI’s model maintenance strategy.
1: Oracle Cloud Infrastructure Data Science Documentation, "Model Monitoring and Retraining".

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.
1: Oracle Cloud Infrastructure ADS SDK Documentation, "Correlation Visualization Methods".

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.
1: Oracle Cloud Infrastructure Load Balancing Documentation, "Changing Load Balancer Type".