1Z0-1067-25 Question 26
Single answerYou have been assigned to standardize the provisioning and maintenance of a fleet of compute instances running an internal application on Oracle Cloud Infrastructure (OCI). The team wants to automate configuration changes, manage environment variables, and keep these changes in version control for easy rollback if issues arise. Which approach best fulfills these requirements?
- A
Store shell scripts in OCI Object Storage and run them manually on each instance whenever configuration changes are required.
- B
Use Oracle Resource Manager to manage all custom application-level configurations by writing them entirely as Terraform code.
- C
Use a configuration management tool (e.g., Ansible or Puppet), storing playbooks or manifests in a Git repository, and integrate with Oracle DevOps for CI/CD-based deployments.
- D
Maintain all environment configurations in a shared file system accessible by compute instances, updating configuration files manually as changes occur.
Show answer and explanation
Correct answer: C
Explanation
Configuration management tools (such as Ansible, Puppet, or Chef) give you more granular control over application-level settings, environment variables, and package management. Storing these configurations in a Git repository and integrating with OCI-based DevOps ensures that all changes are traceable, testable, and reversible. For more details, consult the Oracle Cloud Infrastructure documentation on DevOps and Configuration Management Tools, which outlines recommended best practices to maintain consistency across OCI environments and enable automated rollbacks where necessary.
- A. Incorrect.
Option 1 is incorrect because manually running shell scripts from Object Storage for each instance does not provide continuous management or straightforward rollback. It also lacks automated enforcement of desired configurations.
- B. Incorrect.
Option 2 is partially correct in that Oracle Resource Manager and Terraform are excellent for infrastructure provisioning, but Terraform alone is not designed for in-depth application-layer configuration or for continuous configuration enforcement with version control on each instance.
- C. Correct.
Option 3 is correct. Using a configuration management tool (like Ansible or Puppet) and storing your configuration files (playbooks or manifests) in Git allows you to version those files. Integrating with Oracle DevOps (or similar CI/CD tool) ensures automated deployment of configurations, providing controls for rollback and continuous management.
- D. Incorrect.
Option 4 is incorrect because relying on a shared file system and manually updating configurations does not offer version control benefits, nor does it provide an automated method for rolling back or consistently enforcing configurations across all instances.