The Kubernetes Master node is the central control plane responsible for managing the cluster's resources and orchestrating workload deployment. Its primary responsibilities include:
Scheduling: Deciding which workloads (pods) should run on which worker nodes, based on resource availability and scheduling constraints.
Resource Allocation: Allocating resources to workloads to ensure optimal utilization across nodes.
Cluster Management: Maintaining the desired state of applications, managing cluster events, and ensuring that all the components of the cluster are functioning properly.

Step 1: Understanding the Requirement
The objective is to store the resulting build output from a Build Pipeline in a container repository. In OCI DevOps, the build output is stored as an artifact, which can include Docker images or other build-generated files. To store these artifacts in a container repository, you need to explicitly deliver artifacts in the pipeline.
Step 2: Explanation of the Options
A . Trigger deployment
This stage is used to trigger a deployment pipeline, which comes after the artifacts are already stored and prepared for deployment.
Not applicable: This stage is downstream of storing artifacts and is used for deploying software, not for saving the build output to a repository.
B . Managed build
The managed build stage is where you compile, test, and package the application. This has already been completed successfully according to the question.
Not applicable: The question specifies that the build has been completed, so this stage is not relevant at this point.
C . Deliver artifacts
The Deliver Artifacts stage in OCI DevOps pipelines is designed to store the output of the build process in an artifact repository, such as:
OCI Container Registry (OCIR) for Docker images.
Artifact Registry for build artifacts like binaries or JAR files.
Applicable and Correct Answer: This is the correct next step for storing the resulting D . Export packages This is not a standard OCI DevOps pipeline stage. It may be relevant in other contexts but is not related to OCI DevOps for storing build artifacts.
Step 3: Key Concepts of "Deliver Artifacts" in OCI DevOps
Purpose: Save build outputs (artifacts) to an artifact repository.
Artifact Types: Includes Docker container images, binaries, JAR files, or other build outputs.
Repositories Supported:
OCI Container Registry (OCIR)
OCI Artifact Registry
Configuration:
Specify the artifact source (build stage output).
Define the destination repository (e.g., OCIR).
Step 4: References and OCI Resources
OCI DevOps Build Pipelines:
Build Pipeline Documentation
Deliver Artifacts Stage
OCI Container Registry (OCIR):
OCI Container Registry Overview
OCI Artifact Registry:
OCI Artifact Registry Overview

OCI Container Instances are a serverless compute service that allows you to run containerized workloads without managing the underlying infrastructure. Oracle Cloud Infrastructure (OCI) manages provisioning, patching, and all the ongoing server management tasks, providing a fully managed environment.

ansh81vru1zp is the <tenancy-namespace>. In Oracle Cloud Infrastructure Registry (OCIR), the tenancy namespace uniquely identifies the tenancy and is used as part of the image path.
iad is the <region-key>. The region key is the shorthand identifier for the OCI region (iad represents Ashburn region), and it is used in the fully qualified path for images stored in the Oracle Cloud Infrastructure Registry (OCIR).

Resources provisioned through OCI Resource Manager (RM) can still be modified or destroyed from outside of RM, such as using the OCI Console, CLI, or other APIs. RM manages the lifecycle of resources created by its Terraform configurations, but it does not prevent other tools or methods from modifying or deleting those resources.