100+ Free Pipelines with Tekton Practice Questions

Prepare for the Pipelines with Tekton (SC106) exam with instant access — no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

100+ Questions

100% Free

Loading practice questions...

Same family resources

Explore More DevOps & CI/CD Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

JFrog Artifactory Certified DevOps Engineer

Practice Questions100 questions

2026 Statistics

Key Facts: Pipelines with Tekton Exam

$79

Exam Fee (USD)

The Linux Foundation

45 min

Exam Duration

The Linux Foundation

Online proctored

Performance-based and/or MCQ

The Linux Foundation

Non-expiring

Credential Validity

The Linux Foundation

Not published

Passing Score

The Linux Foundation

CNCF

Tekton Upstream Home

Tekton / Cloud Native Computing Foundation

Pipelines with Tekton (SC106) is a $79, 45-minute, online proctored Linux Foundation SkillCred with performance-based and/or multiple-choice items; the passing score and question count are not published, and the credential does not expire. It covers Tekton fundamentals, Tasks/TaskRuns, Pipelines/PipelineRuns, Triggers, secrets, and the tkn CLI.

Sample Pipelines with Tekton Practice Questions

Try these sample questions to test your Pipelines with Tekton exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1Tekton Pipelines is built as an extension to Kubernetes. How does Tekton add its custom types such as Task, Pipeline, and PipelineRun to a cluster?

A.By installing a set of Custom Resource Definitions (CRDs) and a controller that reconciles them

B.By replacing the Kubernetes API server with a Tekton-specific server

C.By running every Task as a standalone Helm release

D.By storing pipeline definitions only in an external database outside the cluster

Explanation: Tekton installs Custom Resource Definitions (CRDs) like Task, Pipeline, TaskRun, and PipelineRun, plus a controller that watches and reconciles those resources. This lets you define CI/CD building blocks declaratively with kubectl, the same way you manage any native Kubernetes object.

2In Tekton, what is the smallest unit of execution that runs as a single container inside a Task's Pod?

A.A Pipeline

B.A Step

C.A Workspace

D.A TriggerBinding

Explanation: A Step is the smallest building block; each Step runs as one container within the Task's Pod and executes a command or script. Steps in a Task run sequentially in the order they are declared.

3What is the relationship between a Task and a TaskRun in Tekton?

A.A TaskRun is a reusable template and a Task is a single execution of it

B.A Task and a TaskRun are two names for the same resource

C.A Task defines reusable steps while a TaskRun instantiates and executes that Task on the cluster

D.A TaskRun can only be created automatically by a PipelineRun, never on its own

Explanation: A Task is a reusable, parameterized definition of Steps; it does nothing by itself. A TaskRun instantiates that Task with concrete parameter values, workspace bindings, and a service account, then runs it as a Pod on the cluster.

4A Task author wants a Step's command to receive a value supplied at run time, for example an image tag. Which Tekton mechanism should they use?

A.Workspaces

B.Sidecars

C.Results

D.Parameters (params)

Explanation: Parameters declared under a Task's params field accept values at run time and are referenced inside Steps with $(params.name). This is the standard way to make a Task reusable and configurable, such as passing an image tag or a flag.

5Which variable substitution correctly references a Task parameter named 'image-url' inside a Step?

A.$(params.image-url)

B.${params.image-url}

C.{{params.image-url}}

D.%(params.image-url)%

Explanation: Tekton uses the $(...) substitution syntax. A parameter named image-url is referenced as $(params.image-url). For names containing dots you can use bracket notation such as $(params['my.name']).

6A Task parameter is declared with type 'array'. How is the full set of array values expanded when passed to a Step's args?

A.$(params.flags)

B.$(params.flags[*])

C.$(params.flags.all)

D.$(params.flags.length)

Explanation: Array parameters are expanded with the star index, $(params.flags[*]), which substitutes every element as separate arguments. A single element can be referenced by index, for example $(params.flags[0]).

7How does a Step emit a Task result named 'commit' so it appears in the TaskRun status and can be consumed by later Tasks?

A.By printing the value to standard output with a 'result:' prefix

B.By setting an environment variable named RESULT_COMMIT

C.By writing the value to the file at $(results.commit.path)

D.By creating a ConfigMap named commit in the Task's namespace

Explanation: A Task declares results, and a Step writes the value to the file path exposed as $(results.commit.path), which resolves under /tekton/results. Tekton reads that file after the Step completes and surfaces it in the TaskRun status for downstream consumption.

8Tekton imposes a size limit on Task results because they are stored in the TaskRun's status (backed by the container termination message). What is the practical implication for what you store in a result?

A.Results should hold large file contents such as full build logs

B.Results must always be exactly 1 MB in size

C.Results can be of unlimited size as long as they are base64 encoded

D.Results should hold small strings such as image digests, commit SHAs, or version tags

Explanation: Results are stored in the Pod's termination message, which has a small size limit (historically around 4 KB total across results). Use them for short identifiers like image digests, commit SHAs, or tags; large data should be passed through a Workspace instead.

9What is the primary purpose of a Workspace in a Tekton Task?

A.To provide a shared filesystem location, such as for source code or a cache, backed by a volume

B.To pass small string values between Tasks

C.To define the order in which Tasks run

D.To expose an HTTP endpoint for incoming webhooks

Explanation: A Workspace is a shared filesystem mounted into a Task's Steps, backed by a volume such as a PersistentVolumeClaim, emptyDir, ConfigMap, or Secret. It is the right mechanism for sharing larger data like a cloned repository or a build cache.

10Inside a Step, which variable resolves to the mounted filesystem path of a Workspace declared with the name 'source'?

A.$(params.source.path)

B.$(workspaces.source.path)

C.$(results.source.path)

D.$(workspaces.source.volume)

Explanation: A Workspace's mount location is referenced with $(workspaces.<name>.path). For a Workspace named source, $(workspaces.source.path) gives the directory where Steps can read and write shared files.

About the Pipelines with Tekton Exam

Pipelines with Tekton (SC106) is a Linux Foundation SkillCred that validates the ability to automate continuous delivery workloads on Kubernetes using Tekton. It tests the core Tekton model: Tasks and TaskRuns (Steps as containers, params, results written under /tekton/results, and workspaces), Pipelines and PipelineRuns (ordering with runAfter and result dependencies, when expressions, matrix fan-out, and finally tasks), and Triggers for event-driven pipelines (EventListener, TriggerBinding, and TriggerTemplate). It also covers reusability through remote resolution and the Tekton Hub, consuming secrets and tokens via ServiceAccount-linked credentials and workspaces, and operating with the tkn CLI for starting, observing, and debugging runs. The exam is a 45-minute, online, proctored test with performance-based and/or multiple-choice items.

Assessment

Question count not published by the exam provider

Time Limit

45 minutes

Passing Score

Not published

Exam Fee

$79 (The Linux Foundation (CNCF / Tekton))

Pipelines with Tekton Exam Content Outline

~12%

Tekton fundamentals and CI/CD on Kubernetes

Understand Tekton as Kubernetes CRDs plus a controller, the Steps-Tasks-Pipelines execution model, CNCF and CD Foundation governance, the Tekton Hub catalog of reusable Tasks, and cluster configuration via feature-flags such as enable-api-fields.

~26%

Tasks and TaskRuns

Define Steps as containers; configure params of type string, array, and object; emit and consume results via $(results.name.path) under /tekton/results; mount workspaces (PVC, emptyDir, configMap, secret); and use sidecars, stepTemplate, scripts, onError, and remote resolution for reuse.

~30%

Pipelines and PipelineRuns

Order Tasks with runAfter and implicit result dependencies to form a DAG, share data through workspaces and volumeClaimTemplate, gate Tasks with when expressions, fan out with matrix, run cleanup with finally and $(tasks.status), and configure retries and timeouts.

~14%

Triggers and event-driven pipelines

Receive events with an EventListener sink, extract payloads and headers in a TriggerBinding using $(body) and $(header), instantiate PipelineRuns or TaskRuns from a TriggerTemplate using $(tt.params), and filter or verify events with GitHub, GitLab, and CEL interceptors plus correct RBAC.

~6%

Secrets, tokens, and authentication

Attach credential Secrets to a TaskRun's ServiceAccount, annotate them with tekton.dev/git and tekton.dev/docker hosts, inject Secrets through env or secret-backed workspaces, and assign per-task service accounts via taskRunSpecs.

~12%

tkn CLI, debugging, and troubleshooting

Use tkn to start, follow logs, describe, list, cancel, and prune runs; debug failing Steps with breakpoint-on-failure and the /tekton/debug/scripts helpers; and diagnose pending TaskRuns, unbound PVCs, result-reference errors, and credential mismatches.

How to Pass the Pipelines with Tekton Exam

What You Need to Know

Passing score: Not published
Assessment: Question count not published by the exam provider
Time limit: 45 minutes
Exam fee: $79

Keys to Passing

Work through all 100 available questions
Review every answer and explanation
Track weak areas and revisit them
Use our AI tutor for tough concepts

Pipelines with Tekton Study Tips from Top Performers

1Build a small Pipeline by hand: clone with a workspace, build, then a finally Task that reads $(tasks.status), so DAG ordering, workspaces, and finally all become muscle memory.

2Memorize the substitution syntax cold: $(params.x), $(params.x[*]) for arrays, $(results.x.path), $(workspaces.x.path), $(tasks.x.results.y), and $(context.pipelineRun.name).

3Practice Triggers end to end: an EventListener sink, a TriggerBinding using $(body.head_commit.id) and $(header.X-GitHub-Event), and a TriggerTemplate referencing $(tt.params.x).

4Drill error handling and flow control: onError continue versus stopAndFail, retries, per-Task timeout, when expressions with in/notin, and matrix fan-out (remember the Cartesian product).

5Get comfortable with the tkn CLI: tkn pipeline start, tkn pipelinerun logs -f, tkn pipelinerun describe, tkn taskrun logs, and tkn pipelinerun cancel.

6Know the troubleshooting basics: pending TaskRuns from unbound PVCs or quota, credential Secrets linked to the ServiceAccount with tekton.dev/git annotations, and breakpoint-on-failure debugging.

Frequently Asked Questions

What are the exam facts for Pipelines with Tekton (SC106)?

SC106 is a Linux Foundation SkillCred costing $79. It is a 45-minute, online, proctored exam with performance-based and/or multiple-choice items. The passing score and question count are not published, and the credential does not expire.

What does the SC106 exam cover?

It covers Tekton fundamentals on Kubernetes, Tasks and TaskRuns, Pipelines and PipelineRuns, sharing data with workspaces, params and results, error handling, task sequencing, matrix pipelines, Triggers, consuming secrets and tokens, and debugging with the tkn CLI.

Do I need experience or prerequisites to take SC106?

No. The Linux Foundation lists SC106 as a beginner-friendly SkillCred with no formal prerequisites, though it is aimed at DevOps, development productivity, and platform engineers working with Kubernetes CI/CD.

How are Tekton results passed between Tasks?

A Task writes a result to the file at $(results.name.path) under /tekton/results, and a later Task consumes it with $(tasks.taskname.results.resultname). Referencing a result also creates an implicit ordering dependency between the Tasks.

What is the difference between runAfter and a result dependency?

runAfter explicitly forces a Task to wait without passing data, while consuming another Task's result with $(tasks.name.results.x) both passes the value and implicitly orders the Tasks, so an extra runAfter is unnecessary.

Does the SC106 credential expire?

No. The Pipelines with Tekton SkillCred is non-expiring. Candidates receive a 12-month eligibility window to schedule and complete the exam after purchase.