Discuss Linux Foundation CGOA Exam Topic 4 Question 1

In GitOps, what does the principle of Versioned and Immutable mean?

AAll changes to configuration and infrastructure should be made directly on production environments.

BAll software versions should be stored in a Git repository.

CConfiguration and infrastructure code should be version-controlled and treated as immutable artifacts.

DConfiguration and infrastructure code should be modified directly on production environments.

Suggested Answer: C

One of the four fundamental GitOps principles is Versioned and Immutable. This means that the entire system's desired state must be stored in a Git repository with version control. Each change must be represented as a commit, and Git's immutability guarantees a reliable, auditable history of how the system evolved.

''The desired state is stored in a version control system. The record of truth is stored in an immutable history, and changes can be audited and reverted if necessary. This guarantees that the system's configuration is versioned, immutable, and traceable.''

Thus, configuration and infrastructure must be version-controlled and immutable, never changed directly in production.

===========

Get Premium CGOA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

13 comments · newest first

Irving 11 months ago

Wait, are we really treating everything as immutable? Sounds risky!

Micah 11 months ago

Totally agree, immutability helps prevent issues.

Cassandra 11 months ago

B is important too, but C covers it better.

Veronica 11 months ago

No way, A and D are just wrong!

Sharee 11 months ago

C is the right answer! Version control is key.

Walton 12 months ago

I definitely recall that version control is key in GitOps, so I’m leaning towards option C as well, but I need to double-check what "immutable" really implies.

Ryan 12 months ago

I’m a bit confused about the term "immutable." Does it mean we can’t change anything once it's deployed, or just that we track changes?

Tomas 1 year ago

I remember a practice question that emphasized treating infrastructure code as immutable artifacts, so I feel like option C might be the right choice here.

Linwood 1 year ago

I think the principle of Versioned and Immutable relates to how we manage our configurations, but I'm not entirely sure if it's about storing software versions in Git.

Rikki 1 year ago

Yeah, I agree with Bronwyn. The whole point of GitOps is to ensure consistency and traceability by treating infrastructure as code that's version-controlled, not manually updated in production. C is the way to go.

Bronwyn 1 year ago

Okay, I've got it. The versioned and immutable principle means that once infrastructure or config is committed to the Git repo, it can't be changed directly in production. That aligns with answer C.

Martin 1 year ago

Hmm, I'm a bit confused on this one. I know GitOps is about using Git as the single source of truth, but I'm not sure about the immutable part. Let me think this through.

Desiree 1 year ago

I think C is the right answer. The key principles of GitOps are to treat infrastructure and config as immutable code that's version-controlled.

Linux Foundation CGOA Exam - Topic 4 Question 1 Discussion