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.
1: Oracle Cloud Infrastructure Language Documentation, "Text Analysis Features".

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.
1: Oracle Cloud Infrastructure WAF Documentation, "Protection Rules".

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.
1: Oracle Cloud Infrastructure Data Science Documentation, "Jobs Logging".

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 1with C. Other options (A, B, D) relate to different ML stages.
1: Oracle Cloud Infrastructure Data Science Documentation, "Feature Engineering Overview".

Detailed Answer in Step-by-Step Solution:
Objective: Determine where OCI budgets are set.
Understand Budgets: Track spending across OCI resources.
Evaluate Options:
A: Compartments—Scoped within tenancy, not budget root.
B: Instances—Specific resources, not budget scope.
C: Tags—Filter costs, not budget setting.
D: Tenancy—Top-level scope for budgets—correct.
Reasoning: Budgets apply at tenancy, optionally filtered (e.g., by compartment).
Conclusion: D is correct.
OCI documentation states: “Budgets are set at the tenancy level (D), with optional filters like compartments or tags to monitor spending.” A, B, and C are sub-elements—only D is the primary scope per OCI’s cost management.
1: Oracle Cloud Infrastructure Cost Management Documentation, "Setting Budgets".