Blue-Green deployments involve deploying the new version of an application alongside the old version and switching traffic to the latest version once it is ready.
B.
Blue-Green deployments involve deploying the new version of an application to a subset of users and gradually expanding the deployment based on feedback.
C.
Blue-Green deployments involve deploying different versions of an application in other regions and routing traffic based on geographic location.
D.
Blue-Green deployments involve deploying only one version at a time.
Blue-Green deployments are aprogressive delivery patternwhere two environments exist: Blue (current version) and Green (new version). The new version is deployed in parallel, and once validated, traffic is switched over from Blue to Green.
“Blue-Green deployments provide zero-downtime releases by running two production environments: one active and one idle. A new version is deployed to the idle environment, tested, and when ready, traffic is switched to it.â€
Thus, the correct description isA.
[References:GitOps Patterns (CNCF GitOps Working Group), Progressive Delivery patterns., ===========]
Question # 5
In GitOps practices, when does CD take part?
A.
CD takes part simultaneously with CI, both components of GitOps practices.
B.
CD takes part after CI to automate the deployment of applications based on changes in the Git repository.
C.
CD takes part before CI stage in order to ensure the successful deployment of applications.
In GitOps, Continuous Deployment (CD) follows after Continuous Integration (CI). CI is responsible for building and testing application code, while CD automates the delivery and deployment of these changes into runtime environments. The Git repository serves as the single source of truth, and when CI merges new changes into the main branch, CD reconciles the state of the environment to match what is declared in Git.
“GitOps builds on the principles of DevOps by using Git as the source of truth for declarative infrastructure and applications. CI pipelines handle the integration and testing of code, and CD pipelines or agents automatically reconcile the desired state in Git with the actual state in the cluster.â€
This shows that CD is triggered after CI to handle deployment automation, ensuring systems remain in sync with what is declared in version control.
[References: GitOps Principles (CNCF GitOps Working Group), GitOps Working Group Terminology & Principles documents., , ]
Question # 6
What does the GitOps reconciliation loop ensure?
A.
Only applies changes but does not remove resources that used to be part of the Desired State.
B.
That the Desired State is instantaneously applied to the system.
C.
The Desired State is applied to the system when the current system state diverges from the Desired State.
D.
When manifests have errors, it will ensure that as much as possible still gets applied.
The reconciliation loop is a fundamental GitOps principle. It continuously compares thedesired state(stored in Git) with theactual state(running in the system). When a divergence (drift) is detected, the reconciler automatically corrects the system to match the desired state.
“The reconciliation loop ensures the system is continuously converging toward the declared desired state. Whenever the actual state deviates, the loop reconciles the system to match the desired state.â€
Thus, the correct answer isC.
[References:GitOps Principles (CNCF GitOps Working Group).]
Question # 7
What is Infrastructure as Code (IaC)?
A.
An approach to managing infrastructure resources using physical hardware only
B.
A methodology for managing infrastructure resources through graphical user interfaces
C.
A manual process of managing infrastructure resources using the command line
D.
A programming approach to managing and provisioning infrastructure resources through machine-readable definition files
Infrastructure as Code (IaC)is a foundational practice in GitOps. It involves managing and provisioning infrastructure throughdeclarative, machine-readable filesrather than manual processes or GUIs. IaC ensures consistency, automation, and repeatability across environments.
“Infrastructure as Code defines and manages infrastructure through code files stored in version control. This enables automation, reproducibility, and immutability in infrastructure provisioning.â€
Thus,Dis correct.
[References:GitOps Related Practices (CNCF GitOps Working Group)., ===========]
Question # 8
You are working on a GitOps project and need to understand the similarities and differences between pull-based messaging systems and event-driven systems. What is a key difference between these two types of systems?
A.
Pull-based systems require a constant network connection to receive updates.
B.
Event-driven systems are less flexible and scalable compared to pull-based systems.
C.
Pull-based systems are more efficient in handling real-time events.
D.
When only events trigger reconciliation, the system is more vulnerable to drift caused by other things.
In GitOps, thepull-based modelcontinuously reconciles the actual state with the desired state. This makes it resilient to drift, since reconciliation runs regularly. In contrast,event-driven systemsonly reconcile when an event occurs (e.g., a webhook), which makes them more prone to drift if changes happen outside those events.
“A pull-based reconciliation loop ensures continuous alignment with the desired state. Event-driven reconciliation, triggered only on events, risks system drift if changes occur outside those triggers.â€
Thus, the correct answer isD.
[References:GitOps Related Practices (CNCF GitOps Working Group), Reconciliation Models., ===========]