1Z0-1067-25 Question 1
Single answerYour organization manages three separate compartments in Oracle Cloud Infrastructure (OCI) for development, testing, and production. You need to ensure each new environment applies mandatory tags to resources and remains consistent across all compartments. Which approach best achieves this objective?
- A
Use OCI Resource Manager with a single Terraform configuration. Leverage variables for environment-specific details and set up tag defaults in each compartment.
- B
Use the OCI Console to manually deploy resources for each environment, applying tags by hand as needed.
- C
Create environment-specific CLI scripts without referencing any tagging structure, relying on manual checks to ensure tagging compliance.
- D
Maintain separate Resource Manager stacks for each environment, leaving tags optional for teams to apply.
Show answer and explanation
Correct answer: A
Explanation
Using OCI Resource Manager as an Infrastructure as Code (IaC) solution with Terraform is the recommended approach to create consistent, repeatable deployments across multiple environments. Employing variables for environment-specific values allows for easy scalability and maintainability, while configuring tag defaults in each compartment ensures that mandatory tags are automatically and uniformly applied to newly created resources. For further details on tag defaults and Terraform best practices, refer to Oracle� documentation on Resource Manager and managing tags in the OCI console.
- A. Correct.
Option 1 is correct. By using a single Terraform configuration for multiple environments, you can parameterize environment-specific settings through variables, ensuring consistent deployment. Additionally, configuring tag defaults in each compartment guarantees that required tags are automatically applied to any new resource, reducing the risk of manual errors and ensuring uniformity.
- B. Incorrect.
Option 2 is incorrect. While using the OCI Console can work for small environments, manual deployments and tagging often lead to inconsistent configurations and increased operational overhead. It also becomes more challenging to audit and version-control these changes.
- C. Incorrect.
Option 3 is incorrect. Relying on custom CLI scripts without an automated tagging structure complicates compliance and consistency efforts. Human error in updates can result in missing mandatory tags and inconsistencies in deployed resources.
- D. Incorrect.
Option 4 is incorrect. While having separate stacks can make sense for certain scaling or isolation requirements, keeping tags optional undermines the goal of consistent compliance. Mandatory tagging should be enforced through tag defaults or required attributes, not left to individual teams.