1Z0-1067-25 Question 2
Select 2You are creating a new application environment in Oracle Cloud Infrastructure (OCI) using Resource Manager. The environment requires that all compute instances be provisioned in a dedicated compartment with the VM.Standard3.Flex shape, that each resource be tagged with a department cost-tracking key, and that you can easily re-deploy the entire environment if needed. Which two actions must you take to ensure your deployment meets these requirements?
- A
A. Define Terraform variables for the compartment and shape in your configuration, then upload the configuration as a stack to Resource Manager.
- B
B. Explicitly define the compartment and shape in the OCI Console before creating any instances, then import those resources into Resource Manager.
- C
C. Configure a tag namespace with a key for department cost tracking, and reference that key in your Terraform resource definitions.
- D
D. Use a manual workflow to add the department tag to each resource after the instances are provisioned.
Show answer and explanation
Correct answers: A, C
Explanation
To automate resource provisioning with consistent shapes, compartments, and tags, you should leverage Oracle Resource Manager's stack-based workflows. By defining Terraform variables and referencing tags within the Terraform configurations, you ensure each new resource follows your standards without manual intervention. This approach also allows for straightforward environment re-deployment. For more information, refer to the official Oracle Cloud Infrastructure Resource Manager documentation at https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Concepts/resourcemanager.htm.
- A. Correct.
A. Correct. Defining Terraform variables for the compartment and shape allows you to systematically control your resource configuration. Uploading the configuration as a Resource Manager stack ensures that all subsequent deployments match these parameters.
- B. Incorrect.
B. Incorrect. While you can provision resources via the console first and then import them into Resource Manager, this approach is more cumbersome and doesn't inherently guarantee that subsequent resources meet the shape and compartment requirements. It also complicates automation.
- C. Correct.
C. Correct. Creating a tag namespace and tagging key helps enforce consistent cost-tracking. Including that tag reference in your Terraform resource blocks ensures the tag is automatically applied each time those resources are provisioned.
- D. Incorrect.
D. Incorrect. Manually adding tags is error-prone and does not align with the automated approach that Resource Manager provides. To reliably ensure each resource is tagged, you should define the tags in your IaC (Infrastructure as Code) templates or a tagging policy.