Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Linux Foundation CGOA Exam - Topic 4 Question 1 Discussion

In GitOps, what does the principle of Versioned and Immutable mean?
C) Configuration and infrastructure code should be version-controlled and treated as immutable artifacts.
A) All changes to configuration and infrastructure should be made directly on production environments.
B) All software versions should be stored in a Git repository.
D) Configuration and infrastructure code should be modified directly on production environments.

Linux Foundation CGOA Exam - Topic 4 Question 1 Discussion

Actual exam question for Linux Foundation's CGOA exam
Question #: 1
Topic #: 4
[All CGOA Questions]

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

Show Suggested Answer Hide Answer
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.


===========

by Raul at Oct 01, 2025, 10:44 PM

Limited Time Offer

25%

Off

Get Premium CGOA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Irving
9 months ago
Wait, are we really treating everything as immutable? Sounds risky!
upvoted 0 times
...
Micah
9 months ago
Totally agree, immutability helps prevent issues.
upvoted 0 times
...
Cassandra
10 months ago
B is important too, but C covers it better.
upvoted 0 times
...
Veronica
10 months ago
No way, A and D are just wrong!
upvoted 0 times
...
Sharee
10 months ago
C is the right answer! Version control is key.
upvoted 0 times
...
Walton
10 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.
upvoted 0 times
...
Ryan
10 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?
upvoted 0 times
...
Tomas
11 months 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.
upvoted 0 times
...
Linwood
11 months 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.
upvoted 0 times
...
Rikki
11 months 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.
upvoted 0 times
...
Bronwyn
11 months 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.
upvoted 0 times
...
Martin
11 months 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.
upvoted 0 times
...
Desiree
11 months 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.
upvoted 0 times
...

Save Cancel