20 Free CGOA Sample Questions with Answers

How to use these CGOA practice questions

Work through the 20 CGOA sample questions in one sitting without looking anything up. For each question, decide on an answer first, then open the answer and read the explanation, including when you were right, because a correct guess and a correct line of reasoning look identical until the exam rewords the question. Mark every question as right, wrong or guessed, and count a guess as wrong when you score yourself. Give the set about 30 minutes, which is the average time per question on the real exam multiplied by twenty. The aim is to find out which exam domains are already solid and which ones need study before you buy the exam.

The official exam format is 60 questions in 90 minutes, with a passing score of 75%, according to the Linux Foundation documentation checked on 2026-10-23.

With JavaScript enabled, each answer starts collapsed behind a Show answer button so you can test yourself. Without JavaScript, and for any crawler or screen reader that reads the raw page, every answer and explanation is already visible below its question.

These questions were written for GoldenKube practice. They are not copied from the real exam, and nothing on this page tells you what the real exam will ask.

• Read the question twice and underline the constraint words: "most", "least", "first", "only", "not".
• Eliminate options you can prove wrong before you pick between the rest.
• Where a question says to select all that apply, every correct option must be chosen and none of the wrong ones.
• Read the explanation even for questions you got right; it often names the nearby concept the exam likes to swap in.

GitOps Terminology (4 questions)

GitOps Principles (6 questions)

Related Practices (3 questions)

GitOps Patterns (4 questions)

Tooling (3 questions)

Score yourself

The Linux Foundation lists a passing score of 75% for CGOA. On a set of 20 questions that is 15 correct. Reaching 15 here is a useful signal and not a prediction: 20 questions is a small sample, and the real exam covers every domain in its published weights. Use the table below to decide what to do next. Count only the questions you answered correctly without help, and be strict about it: a question you got right for the wrong reason belongs in the missed pile. Then repeat the exercise a few days later with a different set from the full bank so that you are measuring understanding and not memory of these specific questions.

Count your misses per domain, using the headings above. One missed question in a domain is noise; three misses in one domain is a study plan. The practice mode on GoldenKube does this sorting for you by sending you back to the domains where you are weakest.

GitOps Terminology: what it tests

GitOps Terminology is where CGOA checks that you use the words correctly. Expect the definitions of GitOps itself, desired state and actual state, a state store, drift, reconciliation, declarative versus imperative configuration, pull versus push delivery, and what an agent or operator does. Questions are mostly definitions and short scenarios asking which term applies. The trap is loose use of everyday words: a pipeline that applies changes with kubectl from CI is push-based, while an in-cluster agent that fetches and applies is pull-based, and the exam treats that difference as important. Getting the vocabulary exact makes the larger principles domain much easier.

Write a one-line definition for each term, then test yourself by covering the term and recognising it from the definition. Terminology questions are a recognition task, so this drill matches the format.

GitOps Principles: what it tests

GitOps Principles is the largest CGOA domain and centres on the four OpenGitOps principles: the system is described declaratively, the desired state is versioned and immutable, approved changes are pulled automatically, and software agents continuously reconcile actual state with desired state. Questions give a setup and ask which principle it satisfies or violates, or ask what follows from a principle, such as why a Git history gives you an audit trail and a rollback path. A common trap is the word immutable: it describes the stored history of desired state, not the running cluster, and applying changes by hand to a live system breaks the reconciliation principle.

Memorise the four principles in order and attach to each one a concrete consequence, such as rollback by revert or detection of drift. The exam asks for consequences more often than for the list itself.

Related Practices: what it tests

Related Practices places GitOps among its neighbours. Expect continuous integration and continuous delivery, infrastructure as code, DevOps culture, configuration management, and how GitOps relates to platform engineering and to progressive delivery. Questions ask what GitOps adds to a practice or where one practice ends and another begins. The trap is assuming GitOps replaces continuous integration: it does not, because building and testing still happen in a CI system, and GitOps takes over at the point where a change to desired state is merged and delivered. Knowing that boundary resolves many of the questions in this domain. Expect scenario wording that names a practice and asks what it contributes to a delivery process.

Draw a delivery timeline from commit to running workload and mark which stages belong to CI, which to GitOps and which to infrastructure as code. The picture answers the boundary questions directly.

GitOps Patterns: what it tests

GitOps Patterns covers the common ways of organising GitOps in practice. Expect repository layouts such as a monorepo versus several repositories, separating application code from environment configuration, promotion between environments, handling secrets without storing them in plain text, and progressive delivery patterns. Questions describe a team or constraint and ask which layout or pattern fits. The trap is choosing the pattern that sounds most advanced rather than the one that fits the stated constraint, such as separate repositories when the question stresses simplicity for a small team. Read the constraint first and treat the options as candidates to eliminate. When two options both seem workable, choose the one that matches the team size, the risk and the separation of duties that the question states.

For each pattern, write the problem it solves and the cost it adds. Matching a constraint to a pattern is the same exercise the questions ask for.

Tooling: what it tests

Tooling asks what the common GitOps and related tools do. Expect the roles of tools such as Argo CD and Flux as reconciliation agents, Helm and Kustomize for packaging and customising manifests, and the ways tools detect drift, sync and report status. Questions focus on what a category of tool is for, not on exact command syntax. The trap is mixing up a packaging tool with a delivery agent: Helm renders and installs charts, while a GitOps agent keeps the cluster aligned with a repository over time. The domain is the smallest, so a short review of each tool's job is enough.

Keep one line per tool: what it takes in, what it produces, and whether it keeps running. That distinction is what separates the tool types in the answer options.

What a 20-question CGOA sample can and cannot tell you

A set of 20 questions is a screening test, not a measurement. With only a few questions per domain, one lucky guess or one unlucky wording moves your result by five percentage points, and a domain with only two questions behind it says almost nothing about that domain's true strength. The set is also fixed, so after one read-through it measures your memory of these items and not your command of CGOA. Use it to choose where to start studying, not to decide whether you are ready, and then rely on the larger bank, where questions repeat only after a gap and the app tracks which domains stay weak.

A second limit is style. Written practice questions share one author voice, while a real exam draws on many writers and reads differently. Treat any practice score, here or elsewhere, as one input next to the official curriculum, hands-on experience with the technology, and the documentation of the project itself.

A one-week plan after the CGOA sample set

After the sample set, spend a week turning the result into a plan. Start with the domains where you missed questions and read the matching part of the official curriculum before you try more questions, because practice is far more useful once you can explain the topic. Return to practice in short daily sessions, review every missed question the next day, and leave the last day for a fresh mixed set. Keep a simple note of which concepts caused misses; the same three or four ideas usually explain most of them, and naming them is what turns practice into progress.

The largest CGOA domain is GitOps Principles, at 30% of the published weights. If two domains tie for weakest in your tally, start with the heavier one, and keep the other 4 domains ticking over with short reviews.

Adjust the pace to your calendar. If you have more time, spread the same steps over two or three weeks and add a second mixed session at the end of each week. If you have less, keep days 1 to 3 and day 6 and accept a rougher picture. What matters is that every study session starts from a specific weak domain and ends with a check, not that the plan is followed to the letter.

Practice the full CGOA bank

These 20 questions are a small slice of the GoldenKube CGOA bank, which holds more than 250 questions. In practice mode the app serves the questions you are due to review first, then the domain where you are weakest, and it brings missed questions back after a gap until you answer them correctly. You can answer 10 questions as a guest without an account; after that a free account keeps your progress, and no credit card is asked for at any point. Each answer comes with the same kind of written explanation you saw on this page, so a wrong answer is always followed by the reasoning that fixes it.

Practice mode shows one question at a time and gives the verdict and explanation as soon as you answer. A focus option lets you stay inside a single domain until it feels solid, which is the natural next step after finding your weakest domain on this page. There is no timer and no exam simulation in practice mode; the goal is learning, not performance under pressure.

Frequently asked questions