Advanced Flux CD quiz
A free advanced Flux CD quiz with up to 40 multiple-choice questions on GitOps with Kustomizations, HelmReleases, sources, image automation, notifications and multi-tenancy. Written for engineers who use it day to day, with an explanation for every answer.
Loading Quiz...
Preparing your Flux CD Advanced level questions
Browse the 20 medium Flux CD questions, with answers
- A Kustomization must only be applied after another Kustomization that installs CRDs is ready. Which field do you set?
- What does spec.wait: true do on a Flux Kustomization?
- How do you substitute a per-cluster value such as ${cluster_region} into the manifests a Flux Kustomization applies?
- How does Flux decrypt Secrets that are stored encrypted with SOPS in Git?
- What does the --no-cross-namespace-refs=true flag on the Flux controllers do?
- How can a Kustomization apply resources with a tenant's limited permissions instead of kustomize-controller's own?
- What does 'flux diff kustomization my-app --path ./apps/my-app' show?
- How can a HelmRelease take its Helm values from a ConfigMap or Secret?
- Which HelmRelease setting makes helm-controller retry a failed first install?
- What does driftDetection.mode: enabled do on a HelmRelease?
- Which Flux objects work together to update an image tag in Git when a new version is pushed to a registry?
- How does image-automation-controller know which field in a YAML file to update?
- An ImagePolicy should pick the newest 1.x release tag and ignore 2.0 and later. Which policy fits?
- How can a push to Git make Flux fetch the new commit right away instead of waiting for the GitRepository interval?
- Which Flux setup reports deployment results back to GitHub as commit statuses?
- You delete a Flux Kustomization that has prune: true and no deletionPolicy. What happens to the objects it applied?
- Which file in a Git repository tells source-controller to leave files out of the artifact it builds?
- How can a HelmRelease install a chart that is stored in an OCI registry?
- A GitRepository sets both ref.branch: main and ref.tag: v1.2.0. Which one does Flux check out?
- A Deployment keeps changing and you don't know which Flux object manages it. Which command tells you?