Linux Foundation
CGOA
Q1:
In GitOps, what is a pull-based approach?
○
A
A pull-based approach is when developers manually push changes to the GitOps system, which then applies them automatically.○
B
A pull-based approach is when the GitOps system sends notifications to developers to apply changes from the Git repository manually.○
C
A pull-based approach is when the Git repository automatically pushes changes to the GitOps system, which then applies them.○
D
A pull-based approach is when the GitOps system continuously polls the Git repository for changes and applies them automatically.
Linux Foundation
CGOA
Q2:
Which deployment and release pattern involves gradually shifting traffic from an old version of an application to a new one?
○
A
Red/Black Deployment○
B
Canary Deployment○
C
Blue-Green Deployment○
D
A/B Deployment
Linux Foundation
CGOA
Q3:
When using Kustomize, how are resources, configurations, and customizations commonly organized?
○
A
By specifying all resources inline in the customization file.○
B
In separate configuration files for each resource.○
C
In a single configuration file.○
D
Using a combination of folder directories and referenced folder/file paths.
Linux Foundation
CGOA
Q4:
In the context of GitOps, why would you do a rollback?
○
A
To undo a deployment that introduced a critical bug or caused a system failure.○
B
To improve performance and optimize resource utilization.○
C
To create a backup of the current configuration.○
D
To test a new feature in a controlled environment.
Linux Foundation
CGOA
Q5:
In the context of GitOps, which of the following is the primary purpose of Desired State?
○
A
To serve as a blueprint to recreate a system for behavioral consistency.○
B
To store all persistent application data, such as database content.○
C
For monitoring real-time application performance.○
D
To track code changes that developers have made.