Certified GitOps Associate (CGOA) free question 1 / 10 · Domain 1: GitOps Terminology
An architect needs a test for what belongs in the desired state of a system. Which description matches the OpenGitOps glossary?
- The release versions of the workloads, which are the part that changes at release time
- The configuration data that is enough to recreate the system, so that instances of it behave the same way
- The current readings of the running system, so that the agents can compare them with the previous run
- The full contents of the system, including customer records, so that a copy can be restored from the repository
Show the answer and explanation
Answer: B
Why this is correct
The glossary defines desired state as the aggregate of all configuration data that is sufficient to recreate the system so that instances of the system are behaviourally indistinguishable. The test is therefore recreation: if you could rebuild the system from this data and get the same behavior, the data is complete. Persistent application data, such as database contents, is generally outside it.
Why the other options are wrong
"The full contents of the system, including customer records, so that a copy can be restored from the repository" … The glossary says desired state generally does not include persistent application data such as database contents.
"The release versions of the workloads, which are the part that changes at release time" … Release versions are only part of the configuration. The definition covers the aggregate of all configuration data sufficient to recreate the system.
"The current readings of the running system, so that the agents can compare them with the previous run" … Readings of the running system are the actual state. The desired state is the target that the actual state is compared with.
Key points
The desired state is the aggregate of all configuration data that is sufficient to recreate the system so that instances of the system are behaviourally indistinguishable.