1Z0-1067-25 Question 5
Select 2Your organization is preparing to deploy a new microservices-based application in Oracle Cloud Infrastructure (OCI) across separate Development, Testing, and Production compartments. The team needs a consistent way to define and manage infrastructure for each environment, track and review all infrastructure changes, and quickly roll back if necessary. Which TWO approaches align with OCI best practices for deploying and managing these resources?
- A
Use Infrastructure as Code with Terraform managed by OCI Resource Manager, store your Terraform files in a version control repository, and create separate stacks for each environment.
- B
Use a single Terraform stack for all environments, specifying environment variables at runtime from the command line without version control integration.
- C
Implement a CI/CD pipeline that automatically runs Terraform validation and plan steps in the Development and Testing compartments first, then applies changes to Production upon approval, storing all Terraform code in a Git repository.
- D
Manually provision identical resources in each environment using the OCI Console and keep configuration details in an offline spreadsheet for tracking changes.
- E
Use a locally stored custom script with the OCI CLI to generate resource definitions in YAML files, updated separately for each environment without a shared repository.
Show answer and explanation
Correct answers: A, C
Explanation
Oracle Cloud Infrastructure recommends using Infrastructure as Code (IaC) and a version control system to ensure consistency, repeatability, and traceability across your environments. By adopting Terraform with OCI Resource Manager and integrating with CI/CD pipelines, teams can validate changes in Development and Testing compartments before safely promoting them to Production. For additional guidance, consult the OCI Resource Manager documentation at https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resource-manager-overview.htm.
- A. Correct.
Correct. Managing resources with Infrastructure as Code and using OCI Resource Manager for separate Terraform stacks in each environment is a recommended approach. Storing the Terraform files in a version control system (like Git) allows you to track, review, and roll back changes easily.
- B. Incorrect.
Incorrect. Using a single Terraform stack without version control provides limited visibility into environment-specific changes and makes it challenging to audit or roll back configurations over time.
- C. Correct.
Correct. A CI/CD pipeline that validates and plans Terraform changes in lower environments before applying them in Production follows best practices. Storing code in a Git repository ensures consistent tracking, review, and rollback capabilities.
- D. Incorrect.
Incorrect. Manually replicating resources across multiple environments is prone to human error and does not provide a straightforward method for auditing or rolling back changes, which goes against recommended Infrastructure as Code practices.
- E. Incorrect.
Incorrect. While the OCI CLI is useful, storing YAML definitions in a local directory without a centralized version control system or automation introduces complexity. It does not offer the same repeatability and traceability as Terraform-based Infrastructure as Code with proper version control.