1Z0-997-25 Question 169
Select 2Your organization recently discovered unplanned cost overruns in the Dev compartment caused by unauthorized HPC shape usage. You want to prevent any new HPC resources from being provisioned in the Dev compartment and receive advance notification if your total monthly spend approaches $10,000. Which two strategies should you implement to satisfy these governance and cost-control requirements?
- A
Create a Usage Limit (Quota) policy that disallows HPC shapes in the Dev compartment
- B
Set a monthly cost Budget with threshold notifications at 85% of $10,000
- C
Enable the default Resource Limit Enforcement across the entire tenancy
- D
Distribute custom IAM credentials to track team usage individually
- E
Use a Firewall rule to block HPC shape creation at the subnet level
Show answer and explanation
Correct answers: A, B
Explanation
To enforce governance and reduce cost overruns in OCI, it is critical to leverage Quota policies to restrict resource types (such as HPC shapes) and Budgets to monitor and control spending. Quota policies target the specific compartment and resource shape, while Budgets provide threshold-based notifications to track and control cloud expenses proactively. For more details, refer to Oracle's documentation on 'Managing Quotas' and 'Budgets' in the OCI Cost Management Guide.
- A. Correct.
Option 1 is correct. A Usage Limit (Quota) policy can explicitly restrict HPC shapes within a specific compartment (Dev in this case). This ensures no new HPC resources can be provisioned there, directly addressing the unauthorized shape usage problem.
- B. Correct.
Option 2 is correct. Budgets in OCI allow you to set thresholds (for example, at 85%, which is a common best practice) and send alerts when spending nears the budget limit. This prevents unexpected cost overruns by giving you advance warning before costs exceed your target.
- C. Incorrect.
Option 3 is incorrect. Resource Limit Enforcement sets the maximum number of certain resource types across the tenancy, but it does not selectively block HPC shapes in a specific compartment or handle budget alerts. It is not specifically tailored to your Dev compartment or cost threshold requirements.
- D. Incorrect.
Option 4 is incorrect. Distributing custom IAM credentials only helps identify usage by user or group. It does not inherently prevent HPC shape creation or provide cost alerts. Without quotas or budgets, cost spikes can still occur.
- E. Incorrect.
Option 5 is incorrect. Using a firewall (e.g., OS-level firewall rules or network security) does not manage HPC shape creation. Firewalls control network traffic and cannot directly restrict provisioning of compute resources inside OCI.