Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A development team is implementing a new cloud-native application and wants to ensure that all changes to the infrastructure and application configuration are trackable, auditable, and reversible. They decide to adopt a practice where the desired state of the system is declared in a version-controlled repository, and automated processes continuously reconcile the live state with this declared state. Which cloud-native architecture principle are they adopting?
- AService-Oriented Architecture (SOA)
- BGitOps
- CEvent-Driven Architecture
- DMonolithic Architecture
Show answer & explanationAnswer & explanation
Correct answer: B. GitOps
GitOps ensures that the desired state of the system, including infrastructure and application configurations, is declared in a version-controlled Git repository. Automated reconciliation processes then continuously work to match the live system state to this declared state, providing traceability and auditability.
Why the other options are wrong
- A. Service-Oriented Architecture (SOA) is a software architecture pattern, not a principle for managing infrastructure state.
- C. Event-Driven Architecture focuses on communication via events, not infrastructure as code or reconciliation.
- D. Monolithic Architecture is an application structure where all components are tightly coupled, which is opposite to cloud-native principles.
GitOps
An operational framework that takes DevOps best practices used for application development, like version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation.
- Git as the single source of truth.
- Declarative configuration.
- Automated reconciliation.
- Observable and auditable changes.
Memory trick: Git is the grand master of Ops.