1Z0-1067-25 Question 50
Select 3Your company� development team runs 50 always-on Compute instances in Oracle Cloud Infrastructure (OCI). These instances are only actively used during regular business hours but remain running 24/7, causing unexpected increases in monthly costs. The finance department has asked you to optimize costs without sacrificing rapid access to these resources for daytime development work. Which three strategies should you implement to effectively reduce costs while ensuring the team can quickly restore or scale resources?
- A
Switch to High Performance Computing (HPC) shapes for all development workloads
- B
Implement scheduled stop/start policies to power down or reduce shape sizes after business hours
- C
Leverage tagging to categorize and track underutilized resources in the development environment
- D
Migrate all mission-critical data to ephemeral block storage to save costs
- E
Utilize OCI Budgets and Cost Analysis to set spending thresholds and alert notifications
Show answer and explanation
Correct answers: B, C, E
Explanation
To optimize OCI spend, it is essential to target resources that remain underutilized during off-peak hours, leverage proper resource categorization and tagging, and actively monitor and manage cloud usage. Scheduled stop/start policies allow the environment to be scaled down when not in use, while tagging and continuous visibility through budgets and cost analysis tools enable data-driven decisions. Refer to Oracle documentation on 'Managing Budgets and Alerts' and 'Using Tagging for Resource Management' for best practices and detailed implementation steps.
- A. Incorrect.
Option 1: Switch to High Performance Computing (HPC) shapes for all development workloads. (Incorrect) HPC shapes are designed for compute-intensive workloads and are generally more expensive than standard shapes. Unless the workloads specifically require high-performance compute resources, this approach would likely increase costs rather than reduce them.
- B. Correct.
Option 2: Implement scheduled stop/start policies to power down or reduce shape sizes after business hours. (Correct) Automatically stopping instances or scaling them down during off-peak hours is a proven cost optimization technique. It ensures that you are not paying for idle CPU or memory resources when no one is actively using the environment.
- C. Correct.
Option 3: Leverage tagging to categorize and track underutilized resources in the development environment. (Correct) Tagging allows you to identify resources that might be unnecessary or oversized. By collecting detailed usage data under proper tags, you can target specific instances or services for scaling down or shutdown schedules, leading to cost savings.
- D. Incorrect.
Option 4: Migrate all mission-critical data to ephemeral block storage to save costs. (Incorrect) Ephemeral block storage is not intended for long-term, critical data because it does not persist if the instance is stopped or terminated. While it can reduce storage costs for temporary data, it poses a high risk for mission-critical data requiring persistent, reliable storage.
- E. Correct.
Option 5: Utilize OCI Budgets and Cost Analysis to set spending thresholds and alert notifications. (Correct) By setting budgets with alerts, you can monitor spending in real time and quickly take corrective actions if costs exceed anticipated thresholds. This helps maintain visibility and control over resource spending.