1Z0-1067-25 Question 28
Single answerYou need to manage and maintain consistent configurations for several Oracle Cloud Infrastructure (OCI) environments across multiple compartments. Your organization wants to automatically detect if any unintended changes (drift) occur and easily roll back to a known good state. You decide to adopt a configuration management tool that integrates smoothly with OCI, particularly leveraging OCI Resource Manager for automated provisioning. Which approach best meets your requirements?
- A
Use Terraform configurations alongside OCI Resource Manager to define, deploy, and track resource changes for each environment.
- B
Rely on manual updates in the OCI Console and maintain a spreadsheet to track configuration changes across compartments.
- C
Mix shell scripts with custom API calls to OCI, storing all deployment scripts in a shared file server.
- D
Implement Chef Cookbooks and manage drift detection using custom auditing code that queries OCI events.
Show answer and explanation
Correct answer: A
Explanation
Infrastructure-as-code solutions, like Terraform, are generally recommended for OCI because they integrate with OCI Resource Manager. This enables automated provisioning, drift detection, and version-controlled deployments. Oracle documentation (e.g., https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm) strongly suggests using Terraform-based workflows for consistent and trackable infrastructure changes.
- A. Correct.
Correct. Terraform is the recommended infrastructure-as-code approach for OCI. When used with OCI Resource Manager, Terraform templates can define all environment configurations, quickly detect drift, and roll back to a stable configuration if needed. This integration provides version control, automated provisioning, and a clear audit trail.
- B. Incorrect.
Incorrect. Relying on manual changes in the console combined with a spreadsheet is highly prone to errors and does not provide an automated way to detect or revert drift. This approach violates best practices for consistent and traceable configuration management.
- C. Incorrect.
Incorrect. While shell scripts and API calls can automate certain aspects, they lack the robust drift detection, state management, and version control that Terraform and OCI Resource Manager provide. Maintaining custom scripts also increases complexity and risks inconsistent deployments across compartments.
- D. Incorrect.
Incorrect. Chef is a popular configuration management tool but does not have native integration with OCI Resource Manager for seamless drift detection or rollback. Setting up custom event-based auditing code can be very complex and is less straightforward than Terraform's built-in state management features.