First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Oracle Cloud Infrastructure DevOps
In an OCI DevOps build pipeline, which stage type runs a command inside a container image you specify, such as a Maven or Gradle build?
- Trigger stage
- Deliver Artifact stage
- Wait stage
- Managed Build stage Correct answer.
Explanation
A Managed Build stage executes shell commands inside a build runner container image chosen from a container registry, which is how compile and unit-test steps are performed. It is the only build pipeline stage that actually runs user commands.
Question 2Oracle Cloud Infrastructure DevOps
Which OCI DevOps artifact type is used to store a generic binary produced by a build pipeline in an OCI Object Storage bucket?
- Generic artifact Correct answer.
- Deployment pipeline artifact
- Container image artifact
- Kubernetes manifest artifact
Explanation
A generic artifact represents any deliverable stored as an object in an Object Storage bucket, such as a JAR, ZIP, or tarball. Container image artifacts reference a container registry repository instead, and a Kubernetes manifest artifact is a specialized type for YAML deployment specs.
Question 3Oracle Cloud Infrastructure DevOps
What is the primary purpose of a trigger in an OCI DevOps project?
- To grant build runners permission to pull from a container registry
- To define the approval gate before production deployment
- To promote an artifact between deployment environments
- To start a pipeline automatically in response to a source code event or a schedule Correct answer.
Explanation
Triggers connect source control events, such as a push or pull request merge in a DevOps code repository, or a schedule, to automatic pipeline execution. They are the automation entry point rather than an authorization or promotion mechanism.
Question 4Oracle Cloud Infrastructure DevOps
Which OCI service must a container image artifact reference so that a deployment pipeline can pull the image onto OKE nodes?
- OCI Container Registry repository Correct answer.
- OCI Artifact Registry repository
- OCI File Storage file system
- OCI Object Storage bucket
Explanation
Container image artifacts in OCI DevOps are backed by repositories in OCI Container Registry (OCIR). The deployment pipeline and cluster nodes authenticate to OCIR to pull the image.
Question 5Oracle Cloud Infrastructure DevOps
A team wants a deployment pipeline to pause and require a human decision before releasing to production. Which stage type should they add?
- Approval stage Correct answer.
- Trigger stage
- Managed Build stage
- Wait stage
Explanation
The approval stage blocks the deployment pipeline until an authorized approver acts on the request. This enforces human control before sensitive environments.
Question 6Oracle Cloud Infrastructure DevOps
Which OCI DevOps construct groups pipelines, artifacts, triggers, and connections for a single application?
- Compartment
- Notification topic
- Dynamic group
- DevOps project Correct answer.
Explanation
A DevOps project is the logical container that holds build pipelines, deployment pipelines, artifacts, triggers, and connections. Compartments provide IAM scoping but are not DevOps-specific grouping objects.
Question 7Oracle Cloud Infrastructure DevOps
Which statement correctly describes the relationship between a build pipeline and a deployment pipeline in OCI DevOps?
- A deployment pipeline must be triggered by the same trigger object as the build pipeline.
- A deployment pipeline can contain Managed Build stages that compile source code.
- A build pipeline directly deploys to OKE without a deployment pipeline.
- A build pipeline produces artifacts, and a deployment pipeline consumes them to release to environments. Correct answer.
Explanation
Build pipelines compile and package deliverables into artifacts, while deployment pipelines take those artifacts and roll them out to environments such as OKE or Compute. The two are linked by artifact references.
Question 8Oracle Cloud Infrastructure DevOps
What does a DevOps connection in a project represent?
- A VPN tunnel between on-premises hosts and OCI
- A private endpoint for Object Storage
- A saved reference to an external system such as GitHub or GitLab used by triggers Correct answer.
- A peering link between two VCNs
Explanation
A connection stores the details and credentials needed to integrate OCI DevOps with external repositories like GitHub, GitLab, or Bitbucket, so triggers can receive events from them. It is not a network construct.
Question 9Oracle Cloud Infrastructure DevOps
An engineer needs the build runner to read a secret token without hardcoding it in the build specification. Which approach fits OCI DevOps?
- Commit the token to the code repository and read it at runtime
- Embed the token in the container image label
- Reference an OCI Vault secret from the build pipeline parameters Correct answer.
- Store the token in the build_spec.yaml under a variables section as plaintext
Explanation
Pipeline parameters can reference secrets stored in OCI Vault, which the build runner injects at execution time without exposing them in the spec file. This keeps credentials out of source control and configuration artifacts.
Question 10Oracle Cloud Infrastructure DevOps
Which build specification file name does an OCI DevOps build pipeline expect by default at the root of the source repository?
- manifest.yaml
- devops.yaml
- pipeline.json
- build_spec.yaml Correct answer.
Explanation
The build pipeline reads a build specification, conventionally named build_spec.yaml, which defines stages, steps, and output artifacts. The pipeline stage can point to a different path if the team chooses.
Question 11Oracle Cloud Infrastructure DevOps
A team wants the build pipeline to output a JAR and also publish it as a generic artifact. What must the build spec declare?
- A connection to GitHub
- A trigger section with a schedule
- A deployment stage targeting OKE
- An outputArtifacts section naming the artifact and the source path Correct answer.
Explanation
The build specification declares output artifacts with a name matching an artifact defined in the project, plus the path produced by the build steps. The pipeline then uploads that path to the artifact's backing store.
Question 12Oracle Cloud Infrastructure DevOps
Which IAM mechanism lets build runner instances use OCI services without storing user credentials?
- Instance principals through a dynamic group with policies Correct answer.
- Static API keys stored in the build spec
- A pre-authenticated request URL
- A user's auth token committed to the repository
Explanation
Dynamic groups match build runner instances by rule, and policies grant those instances permissions via instance principals. This removes the need for long-lived user credentials in the build environment.
Question 13Oracle Cloud Infrastructure DevOps
In a deployment pipeline, which stage type actually rolls a new container image onto an OKE cluster?
- Deploy to OKE stage Correct answer.
- Trigger stage
- Managed Build stage
- Wait stage
Explanation
The Deploy to OKE stage applies Kubernetes manifests and updates workloads on a specified cluster. Other stage types either pause or build and do not perform the rollout.
Question 14Oracle Cloud Infrastructure DevOps
How does a deployment pipeline know which Kubernetes manifest to apply during a Deploy to OKE stage?
- It reads the manifest from the OKE cluster's ConfigMap automatically
- It parses the container image label for manifest content
- It references a Kubernetes manifest artifact containing the YAML Correct answer.
- It downloads the manifest from the source repository at deploy time
Explanation
The stage references a Kubernetes manifest artifact, which stores the YAML to apply, optionally with parameter substitution. The pipeline does not fetch manifests from source control or infer them from image metadata.
Question 15Oracle Cloud Infrastructure DevOps
A build pipeline must run a step only after a previous step succeeds, and the second step should run in the same container. How should the build spec be structured?
- As a single step with a compound shell command
- As multiple steps within one stage Correct answer.
- As separate stages, each with its own container
- As separate pipelines chained by triggers
Explanation
Steps within a single stage share the same container and execute sequentially, so a later step runs only if earlier steps succeed. Separate stages use separate containers and lose in-container state.
Question 16Oracle Cloud Infrastructure DevOps
Which statement best describes how a trigger for an OCI DevOps code repository reacts to a push?
- It polls the repository every hour for changes
- It requires a manual approval before starting the pipeline
- It receives an event from the repository and starts the configured pipeline Correct answer.
- It only fires when a tag is created, never on branch pushes
Explanation
Triggers for OCI DevOps code repositories fire on repository events such as pushes and start the linked pipeline automatically. They are event-driven rather than polling-based.
Question 17Oracle Cloud Infrastructure DevOps
A team wants the same deployment pipeline to deploy to dev, test, and prod sequentially with approvals between them. What is the recommended approach?
- Use one deployment pipeline with multiple stages and approval stages between environment stages Correct answer.
- Create three separate projects, one per environment
- Use a single Deploy to OKE stage targeting all clusters at once
- Rely on triggers to sequence environments
Explanation
A single deployment pipeline can chain environment deployment stages with approval stages between them to enforce promotion order. Separate projects or a single multi-cluster stage lose the controlled promotion.
Question 18Oracle Cloud Infrastructure DevOps
Which OCI service is used to store the secret referenced by a DevOps pipeline parameter?
- OCI Monitoring
- OCI Logging
- OCI Notifications
- OCI Vault Correct answer.
Explanation
OCI Vault stores secrets and keys, and pipeline parameters can reference vault secrets so they are injected securely at runtime. Logging, Monitoring, and Notifications do not store secrets.
Question 19Oracle Cloud Infrastructure DevOps
Where does an OCI DevOps pipeline write logs and execution details for troubleshooting a failed build?
- To a VCN flow log
- To the pipeline run's build or deployment log, viewable in the DevOps console Correct answer.
- To the OKE node's local disk only
- To an Object Storage bucket chosen by the user
Explanation
Each pipeline run records logs and step-level details that can be inspected in the DevOps console or via the API. This is the primary troubleshooting surface for failed steps.
Question 20Oracle Cloud Infrastructure DevOps
A build spec uses a container image from OCIR as the build runner. Which condition must hold for the build to start?
- The build runner must be able to authenticate to OCIR to pull the image Correct answer.
- The image must be stored in Object Storage
- The image must be less than 100 MB
- The image must be public without authentication
Explanation
The build runner needs permission to pull the specified image from OCIR, typically through policies that allow the service or instance principal to read the repository. Public access is not required, and images are not stored in Object Storage.
Question 21Oracle Cloud Infrastructure DevOps
Which OCI DevOps feature lets you substitute environment-specific values into a Kubernetes manifest at deployment time?
- Dynamic group rules
- Trigger filters
- Build spec output artifacts
- Manifest parameter substitution using pipeline parameters Correct answer.
Explanation
Kubernetes manifest artifacts support parameter substitution, where placeholders in the YAML are replaced by pipeline parameter values at deploy time. This avoids maintaining a separate manifest per environment.
Question 22Oracle Cloud Infrastructure DevOps
A pipeline must deploy only when the artifact was built from the main branch. Which design best enforces this?
- Add a Wait stage before deployment
- Use a generic artifact instead of a container image artifact
- Configure the trigger to fire only for the main branch and filter on the source reference Correct answer.
- Rely on the OKE cluster to reject non-main images
Explanation
Branch scoping is enforced at the trigger and filter level, so pipelines start only for the intended source reference. This keeps non-main builds from reaching deployment stages.
Question 23Oracle Cloud Infrastructure DevOps
A team wants build runners to pull from a private OCIR repository and push artifacts to Object Storage without user credentials. Which combination achieves this?
- A public OCIR repository and a public Object Storage bucket
- A user API key embedded in build_spec.yaml
- A dynamic group matching build runners, policies granting OCIR read and Object Storage use, and instance principals Correct answer.
- A NAT gateway and a service gateway only
Explanation
Dynamic groups match the build runner instances by rule, and policies grant those principals the needed OCIR and Object Storage permissions. Instance principals then authorize calls without storing user credentials.
Question 24Oracle Cloud Infrastructure DevOps
What happens when a deployment pipeline stage fails mid-rollout to OKE?
- The pipeline run stops at the failed stage and subsequent stages do not execute Correct answer.
- The pipeline automatically rolls back the cluster to a prior manifest
- The pipeline continues to the next stage regardless of failure
- The pipeline converts the deployment stage into a build stage
Explanation
A failed stage halts the pipeline run, and later stages such as further environment deployments or approvals are not reached. Rollback is not automatic; teams design rollback steps explicitly.
Question 25Oracle Cloud Infrastructure DevOps
A team needs a deployment pipeline to run a custom validation script against the cluster before applying manifests. Which approach fits OCI DevOps?
- Rely on the approval stage to run the script
- Add a Shell or command step in a stage that runs before the Deploy to OKE stage Correct answer.
- Put the script in the Kubernetes manifest artifact
- Use a trigger to execute the script
Explanation
Deployment pipelines support stages that execute commands, allowing validation steps to run before the deploy stage. Approval stages collect human decisions, and triggers only start pipelines.
Question 26Oracle Cloud Infrastructure DevOps
Which OCI DevOps artifact type is used to represent a Docker image stored in OCI Container Registry so that a deployment stage can reference it?
- A generic artifact that points to an Object Storage object
- A container image artifact that references the OCIR repository path and image digest Correct answer.
- A deployment artifact created automatically by the trigger
- A Kubernetes manifest artifact stored in a code repository
Explanation
OCI DevOps models a container image artifact by referencing the OCIR repository and a specific image reference, typically a digest, so a deployment stage can resolve exactly which image to roll out. Generic artifacts point to Object Storage objects, not container images.
Question 27Oracle Cloud Infrastructure DevOps
A build pipeline must be started automatically whenever a pull request is merged into the main branch of an OCI DevOps code repository. Which trigger configuration accomplishes this?
- A DevOps code repository trigger filtered to the main branch with the pull request action Correct answer.
- A schedule-based trigger that fires every hour
- A connection-based trigger that polls Object Storage
- A deployment pipeline trigger that watches OKE events
Explanation
Code repository triggers subscribe to repository events and can be filtered by branch and by action such as push or pull request merge, which is exactly the merge-to-main scenario. Triggers belong to build pipelines, not deployment pipelines.
Question 28Oracle Cloud Infrastructure DevOps
Where can a team configure a pipeline parameter so that its value is supplied by a secret stored in OCI Vault rather than typed into the build specification?
- Inside the build spec's steps section as a plain environment value
- As an Object Storage pre-authenticated request URL
- As a pipeline parameter whose value source is an OCI Vault secret Correct answer.
- As a comment in the deployment pipeline description
Explanation
Pipeline parameters can be bound to OCI Vault secrets, so the secret value is resolved at runtime and never written into the build specification. Plain environment values in the build spec would expose the value in the repository.
Question 29Oracle Cloud Infrastructure DevOps
Which file in the source repository does an OCI DevOps build pipeline read to determine the steps to execute when no custom path is configured?
- devops.toml in the .oci directory
- pipeline.json at the repository root
- build_spec.yaml at the repository root Correct answer.
- Dockerfile at the repository root
Explanation
By default the build pipeline looks for build_spec.yaml at the root of the checked-out source repository and executes its steps sequentially. A custom path can be configured, but the default is that file name at the root.
Question 30Oracle Cloud Infrastructure DevOps
Which stage type in an OCI DevOps deployment pipeline is responsible for applying Kubernetes manifests to an OKE cluster?
- An approval stage
- A wait stage
- A shell stage that executes on the build runner
- A deploy to OKE stage Correct answer.
Explanation
A deploy to OKE stage performs the actual rollout of manifests and container images to the target OKE cluster. Shell stages run scripts, approval stages gate execution, and wait stages introduce delays.
Question 31Oracle Cloud Infrastructure DevOps
A pipeline needs to deploy to a different OKE cluster in each environment while reusing a single deployment pipeline definition. Which mechanism best supports this?
- Creating a separate project per environment
- Using pipeline parameters to supply the target cluster and environment-specific values at runtime Correct answer.
- Duplicating the pipeline for each environment
- Hardcoding the cluster OCID in the manifest
Explanation
Parameters let one pipeline definition accept environment-specific values such as the target cluster OCID and substitution values at runtime. This avoids maintaining duplicate pipeline definitions for each environment.
Question 32Oracle Cloud Infrastructure DevOps
Which OCI Identity and Access Management construct should be granted to build runners so they can pull from a private OCIR repository without embedding user credentials?
- A user account with an API signing key stored in the build spec
- An auth token committed to the code repository
- A pre-authenticated request on the repository
- A dynamic group matching the build runner instances with a policy granting repository read access Correct answer.
Explanation
Dynamic groups match build runner resources by rule, and policies attached to the dynamic group grant them OCI permissions without long-lived user credentials. This is the standard way to authorize managed build runners.
Question 33Oracle Cloud Infrastructure DevOps
Which OCI service stores the Kubernetes manifests and other deployment input files that a deployment pipeline consumes from a repository?
- OCI DevOps code repository or an external Git repository connected through a connection Correct answer.
- OCI Container Registry
- OCI Logging
- OCI Vault
Explanation
Deployment pipelines read manifests from a configured source repository, which can be an OCI DevOps code repository or an external Git repository reached through a connection. Vault holds secrets, OCIR holds images, and Logging stores logs.
Question 34Oracle Cloud Infrastructure DevOps
A build pipeline has two steps, and the second must run only if the first succeeds while reusing the same workspace. Which build spec structure achieves this?
- A single step that concatenates both scripts with a semicolon
- Two separate build pipelines chained by a trigger
- Two steps in different build specs started by the same trigger
- Two steps in the same build spec, where the second step is not marked to run on failure Correct answer.
Explanation
Steps within one build spec run in order in the same workspace, and execution stops on failure unless a step is configured to run on failure. That gives conditional sequencing without splitting the work across pipelines.
Question 35Oracle Cloud Infrastructure DevOps
A deployment pipeline must pause and require a named approver before the production stage runs. Which stage should be inserted immediately before the production deploy stage?
- An approval stage Correct answer.
- A wait stage of 60 minutes
- A deploy to OKE stage with a manual flag
- A shell stage that prints a message
Explanation
An approval stage blocks pipeline execution until an authorized approver acts, which enforces the human gate before production. Wait stages only delay, and shell stages run scripts without requiring authorization.
Question 36Oracle Cloud Infrastructure DevOps
A build must publish a produced JAR as a versioned artifact that a deployment pipeline can consume later. Which build spec element declares that output?
- A step with the type Command that copies the JAR to /tmp
- An environment variable pointing to the JAR
- A comment in the build spec describing the JAR
- An outputArtifacts section naming the artifact and its source path Correct answer.
Explanation
The build spec declares produced files under outputArtifacts, giving each artifact a name and the path of the produced file so the pipeline can store and later consume it. Copying files or setting variables does not register an artifact.
Question 37Oracle Cloud Infrastructure DevOps
A team wants the deployment pipeline to substitute environment-specific values such as image tags into a Kubernetes manifest at deploy time. Which OCI DevOps capability should they use?
- Kubernetes secrets mounted into the pod
- A shell stage that rewrites the manifest on the build runner
- Object Storage lifecycle rules
- Deployment pipeline parameters referenced as substitution variables in the manifest Correct answer.
Explanation
Deployment pipeline parameters can be referenced as substitution variables inside manifests, so the same manifest works across environments with different values. This keeps environment data out of the committed file.
Question 38Oracle Cloud Infrastructure DevOps
Which statement describes how a connection in an OCI DevOps project is used by a pipeline?
- It schedules automatic pipeline runs.
- It stores the pipeline's execution history.
- It defines the IAM policy for the project.
- It holds credentials or access configuration that lets the pipeline reach an external system such as a Git provider or notification target. Correct answer.
Explanation
A connection encapsulates the access configuration needed to integrate with an external system, such as a third-party Git repository or a notification service. Pipelines reference the connection instead of embedding credentials.
Question 39Oracle Cloud Infrastructure DevOps
A build runner must pull a private base image from OCIR to execute build steps. Which condition must be satisfied for the build to start successfully?
- The build runner's dynamic group must be authorized to read the repository, and the build spec must reference the image properly. Correct answer.
- The build spec must contain the OCIR auth token in plain text.
- The image must be public in OCIR.
- The image must be mirrored into Object Storage first.
Explanation
The managed build runner authenticates through its dynamic group, so a policy must allow it to read the OCIR repository, and the build spec must reference the image correctly. Public access or embedded tokens are not required and are not the recommended pattern.
Question 40Oracle Cloud Infrastructure DevOps
A team wants to be notified in a messaging channel whenever a deployment pipeline fails. Which OCI DevOps feature supports this?
- An Object Storage replication rule
- A Vault secret rotation schedule
- A build spec step that sends email from the runner
- A notification topic configured with the deployment pipeline and a subscription to the messaging channel Correct answer.
Explanation
OCI DevOps notifications associate a notification topic with a project or pipeline and deliver events to subscribed endpoints such as a messaging channel. This is the built-in mechanism for pipeline event alerts.
Question 41Oracle Cloud Infrastructure DevOps
Which statement best describes the relationship between a build pipeline and a deployment pipeline in OCI DevOps?
- Build and deployment pipelines must belong to different projects.
- A deployment pipeline can be started automatically by a build pipeline after artifacts are produced. Correct answer.
- A build pipeline can only be started by a deployment pipeline.
- A deployment pipeline replaces the build pipeline for container workloads.
Explanation
A build pipeline can be configured to start a deployment pipeline once its artifacts are produced, forming an end-to-end flow. The reverse dependency and the requirement for separate projects are not true.
Question 42Oracle Cloud Infrastructure DevOps
A team wants to restrict who can approve a production deployment to members of a specific group. Which configuration enforces this?
- Granting the group manage access on the OKE cluster
- Specifying the approver group or users on the approval stage Correct answer.
- Adding the approvers as subscribers to a notification topic
- Adding the group to the code repository's read policy
Explanation
The approval stage accepts a defined set of approvers or an approver group, and only those identities can act on the gate. Notification subscriptions and unrelated policies do not control who may approve.
Question 43Oracle Cloud Infrastructure DevOps
A pipeline must deploy only artifacts built from the main branch. Which design most reliably enforces this?
- Configuring the trigger and deployment pipeline so only builds from main produce the deployable artifact and start deployment Correct answer.
- Naming the artifact with the branch name
- Adding a comment in the manifest stating the branch name
- Relying on developers to manually start the deployment pipeline
Explanation
Enforcement should be automated: the trigger and pipeline wiring should ensure that only main-branch builds produce and promote the deployable artifact. Manual steps or naming conventions rely on human discipline.
Question 44Oracle Cloud Infrastructure DevOps
A deployment to OKE fails partway through applying manifests. What should the team expect from OCI DevOps by default?
- The OKE cluster is deleted and recreated.
- The pipeline automatically reverts the cluster to the previous commit without any configuration.
- The pipeline silently continues to the next stage.
- The pipeline stops and reports the stage as failed, and rollback behavior depends on the manifest and pipeline configuration. Correct answer.
Explanation
A failed stage halts the pipeline and surfaces the failure for troubleshooting, while rollback is not an unconditional automatic behavior and depends on how the rollout and manifests are configured. The cluster itself is never deleted as a result.
Question 45Oracle Cloud Infrastructure DevOps
A team wants a custom validation script to run against the OKE cluster before manifests are applied. Which approach fits OCI DevOps deployment pipelines?
- A wait stage of five minutes before deployment
- An approval stage that runs kubectl commands
- A build spec step that runs after deployment
- A shell stage placed before the deploy to OKE stage that runs the validation script Correct answer.
Explanation
Shell stages can execute custom scripts within the deployment pipeline, so placing one before the deploy to OKE stage runs validation prior to the rollout. Build spec steps run during the build, not against the cluster at deploy time.
Question 46Oracle Cloud Infrastructure DevOps
An engineer needs to reference a Vault secret inside a build spec step. Which approach keeps the secret out of the repository while making it available to the build?
- Passing the secret as a trigger parameter in the trigger definition
- Binding a pipeline parameter to the Vault secret and referencing the parameter in the build spec Correct answer.
- Writing the secret into the build spec as a comment
- Committing the secret value to a file in the repository
Explanation
Binding a parameter to a Vault secret resolves the value securely at runtime, and the build spec references the parameter name rather than the value. This keeps the secret out of source control and out of trigger definitions.
Question 47Oracle Cloud Infrastructure DevOps
A team uses an external Git provider as the source for a build pipeline. What is required so that OCI DevOps can access the repository?
- A Vault secret containing the repository URL only
- An Object Storage bucket mirroring the repository
- A dynamic group that grants the repository write access to OCI
- A DevOps connection configured for the external provider and referenced by the pipeline Correct answer.
Explanation
Access to an external Git provider is configured through a DevOps connection that holds the provider details and credentials, and the pipeline references that connection. A URL alone or an unrelated bucket does not provide authenticated access.
Question 48Oracle Cloud Infrastructure DevOps
A team wants the same deployment pipeline to deploy to dev, then test, then prod, with an approval between each environment. Which design best achieves this?
- One deploy stage with a wait stage before it
- Three independent deployment pipelines with no approvals
- A single deploy stage that loops over environments
- Sequential deploy stages interleaved with approval stages in one deployment pipeline Correct answer.
Explanation
Deployment pipeline stages execute in order, so sequencing deploy and approval stages in one pipeline yields dev, approval, test, approval, prod. Loops and waits do not create the required per-environment gates.
Question 49Oracle Cloud Infrastructure DevOps
A build pipeline must produce a container image, push it to OCIR, and then trigger a deployment pipeline that rolls it out. Which sequence describes the correct wiring?
- The deployment pipeline builds and pushes the image, then starts the build pipeline.
- The build pipeline builds and pushes the image, declares the image artifact, and starts the deployment pipeline that references that artifact. Correct answer.
- The deployment pipeline pulls the image from Object Storage and applies it.
- The trigger pushes the image directly to OKE without a build pipeline.
Explanation
The build pipeline is responsible for building and pushing the image and declaring the image artifact, and it then starts the deployment pipeline that consumes that artifact. Reversing the roles or bypassing the build pipeline breaks the intended flow.
Question 50Oracle Cloud Infrastructure DevOps
A team needs to troubleshoot why a build step failed. Where should they look for the step's execution output and status?
- In the code repository's commit history
- In the build pipeline run's execution details and logs Correct answer.
- In the Vault secret version history
- In the OKE cluster's audit log only
Explanation
Each build pipeline run records stage and step execution details with logs that show command output and failure status. Cluster audit logs, secret history, and commit history do not contain the build step output.