Expert Kustomize quiz
A free expert Kustomize quiz with up to 40 multiple-choice questions on overlays, patches, generators, components, replacements and kubectl apply -k. Written for engineers who run it in production, with an explanation for every answer.
Loading Quiz...
Preparing your Kustomize Expert level questions
Browse the 20 hard Kustomize questions, with answers
- Why can a component patch resources defined in the overlay that includes it, when a base can't?
- Which field path selects the value of the env var SERVICE_HOST in the container named app, for a replacement target?
- A production overlay lists a remote base with ?ref=main. What's the risk?
- A strategic merge patch adds one item to a list in a custom resource, but the build replaces the whole list. Why?
- A custom resource refers to a generated ConfigMap by name, but after the build it still uses the name without the hash suffix. Why?
- An overlay's configMapGenerator uses the same name as one generated in the base, with no behavior set. What happens?
- A kustomization sets namespace: team-a and includes a ClusterRole. What happens to the ClusterRole?
- In a strategic merge patch, what does $patch: replace inside a container's resources map do?
- A patch target sets name: app. Does it also match a Deployment named app-worker?
- A patch changes the metadata.name of its target, and the build fails. What allows the rename?
- Which query parameter of a remote resource URL sets how long Kustomize waits for the fetch?
- A replacement's target field doesn't exist yet in the target resource. What makes Kustomize add it?
- An overlay sets replicas for a Deployment that a HorizontalPodAutoscaler scales. What happens on each kubectl apply -k?
- A configMapGenerator entry has files: [config/app.properties]. Which key holds the file's content?
- labels sets includeSelectors: false and includeTemplates: true. Where do the labels end up?
- What does the openapi field in a kustomization.yaml provide?
- Two bases included by one overlay both define a ConfigMap named settings in the same namespace. What happens?
- A JSON 6902 patch adds an annotation named example.com/owner. How is that key written in the patch path?
- Why can a kustomization build with the kustomize CLI but fail with kubectl apply -k?
- Why does generatorOptions.immutable: true work well with Kustomize's default hash suffix?