The steps that you would take to delete the specified image are:

• To determine which container is using the image, use the “docker ps -a” command. This command will list all the containers in your system, including their ID, image name, status, etc. You can look for the container that has the image name d123f4e55e12 in its output.
• To delete the container, use the ‘docker rm 0f1262bd1285’ command. This command will remove the container with the ID 0f1262bd1285 from your system. You can also use the -f flag to force remove the container if it is running or paused.
• To delete the docker image, use the ‘docker rmi d123f4e55e12’ command. This command will remove the image with the ID d123f4e55e12 from your system. You can also use the -f flag to force remove the image if it is being used by another container. Verified References: [docker ps - Docker Documentation], [docker rm - Docker Documentation], [docker rmi - Docker Documentation]

The statement that is false about deployment pipeline in OCI DevOps is that using deployment pipeline, you can deploy artifacts to Kubernetes cluster, Instance Group, and OCI Compute Instances. This statement is false because using deployment pipeline, you can deploy artifacts to Kubernetes cluster and Instance Group, but not to OCI Compute Instances. A deployment pipeline is a component of OCI DevOps service that allows you to automate the deployment of your artifacts to various target environments. A target environment is a destination where you want to deploy your artifact, such as a Kubernetes cluster or an Instance Group. An Instance Group is a group of compute instances that share the same configuration and are managed as a single unit. However, OCI DevOps service does not support deploying artifacts directly to individual OCI Compute Instances. Verified References: [Deployment Pipelines - Oracle Cloud Infrastructure DevOps], [Target Environments - Oracle Cloud Infrastructure DevOps], [Instance Groups - Oracle Cloud Infrastructure DevOps]

Explanation

The correct statement is: You need to provision a new stack because Terraform uses immutable in-frastructure. In Oracle Cloud Infrastructure (OCI) Resource Manager, Terraform uses the concept of immutable infrastructure, which means that any changes to the infrastructure are managed through the Terraform code. In this scenario, if you want to add a CIDR block, subnet, and compute instance to your VCN, you would need to make the necessary changes to your Terraform code, create a new stack in Resource Manager, and deploy the updated code. This ensures that the infra-structure is created consistently and according to the desired state defined in the Terraform code. Simply provisioning the new resources in the OCI console and later adding them to the Terraform configuration and state would not be the recommended approach in this case.