Cloud Native Application Delivery

Your team manages a production application with Argo CD. The Application resource has both automated sync and self-heal enabled. An on-call engineer, responding to an incident, manually runs 'kubectl scale deployment web --replicas=8' to handle a traffic spike. The Git manifest still declares 3 replicas. What will Argo CD do?

Your team uses Argo CD to deploy a microservices application. The application requires that a database migration Job completes successfully before the API Deployment starts, and a namespace-level ConfigMap must exist before either. All resources live in the same Git repository under one Application. What is the recommended Argo CD mechanism to control the order in which these resources are applied during a sync?

A team is designing a CI/CD pipeline for a cloud-native application on Kubernetes. Developers push code to a Git repository, and the pipeline must produce an artifact that the cluster can run. In which stage of a typical cloud-native CI/CD flow is the container image built and pushed to a registry?

Your team uses Flux for GitOps delivery. A separate CI pipeline builds and pushes a new container image tag to the registry each time code merges to main. You want new image tags to be deployed automatically without a developer manually editing the manifest in Git. Which Flux capability accomplishes this while keeping Git as the source of truth?

Your platform team uses Argo CD to manage 40 microservices across several environments. Each service currently has its own Argo CD Application manifest, but onboarding a new environment means manually creating dozens of Application objects. You want a single, version-controlled entry point in Git from which Argo CD automatically discovers and manages all the individual Application resources. Which GitOps approach best achieves this?

Your team manages a production cluster with Argo CD following GitOps principles. The Git repository is the single source of truth for the Deployment manifests. During an incident, an engineer runs 'kubectl scale deployment web --replicas=10' directly against the cluster to handle a traffic spike, but does not update the Git repository. Argo CD is configured with automated sync and self-heal enabled. What will happen to the manual change?

Your team currently uses a Jenkins pipeline that runs 'kubectl apply' with cluster credentials stored in the CI system to deploy to production. A security review flags that CI tooling holds long-lived cluster credentials. You are asked to adopt a GitOps approach with Flux to address this. Which characteristic of the GitOps pull-based model directly resolves this concern?

Your team adopts GitOps for a production cluster using Flux. A developer, in a hurry to fix an outage, uses 'kubectl edit deployment' to increase the replica count directly on the cluster. Twenty minutes later, the change is gone and the deployment is back to its original replica count. What is the MOST likely reason this happened?

Your team maintains a Helm chart for an internal payment service. You release a new chart that adds a configurable readinessProbe template and fixes an indentation bug in a template, but the packaged application container image remains exactly the same as the previous release. Which field in Chart.yaml should you increment to correctly reflect this change according to Helm conventions?

Your team maintains a Helm chart for a web application that requires a Redis instance and a PostgreSQL database. Rather than copying those upstream charts into your own templates, you want Helm to automatically fetch and package them as part of your release when you run 'helm dependency update'. Where should you declare these external charts?

A platform engineer is packaging a web application with Helm. They want to store the raw Kubernetes manifest definitions with placeholders that get substituted from configurable inputs at install time. Inside a Helm chart directory, which location is designed to hold these parameterized manifest files?

A new engineer wants to install a community-maintained PostgreSQL chart that is published in a public Helm repository at https://charts.example.com. They have Helm installed but have never used this repository before. Which sequence of commands correctly adds the repository, refreshes the local chart index, and installs the chart as a release named 'db'?

Your team maintains a single Helm chart for a web application that must be deployed to three environments (dev, staging, prod) with different replica counts, image tags, and resource limits. You want to keep one chart while customizing each environment's deployment. What is the recommended Helm approach to achieve this?

Your team packages a web application as a Helm chart. During a `helm upgrade`, a database schema migration Job must run and complete successfully before the new application Deployment pods are rolled out. If the migration fails, the upgrade should not proceed. Which Helm feature lets you order this migration Job to execute at the correct point in the release lifecycle?

A platform engineer runs 'helm install myapp ./chart' in a CI pipeline. On the second pipeline run the command fails with an error stating that a release named 'myapp' already exists in the namespace. The team wants the pipeline to reliably update the existing release if it is present, or create it if it is not, without manually checking release state first. Which command best achieves this?

Your team maintains a Helm chart used across several environments. Before publishing a new chart version, you want to catch structural issues, missing required values, and malformed templates locally as part of the CI pipeline — without connecting to any cluster or performing an installation. Which Helm command is designed for this validation purpose?

Your team has finished developing a Helm chart for an internal payments service. You now need to bundle the chart into a versioned, distributable archive so it can be uploaded to a shared Helm chart repository for other teams to install. Which Helm command produces this archive?

A teammate deployed an application using Helm several weeks ago, and you now need to know exactly which custom values were supplied at install time so you can reproduce the release in a staging cluster. You do not have access to the original values file they used. Which Helm command retrieves the user-supplied values that were applied to the currently deployed release?

Your team upgraded a production application using 'helm upgrade myapp ./chart'. After the upgrade, the pods are crashing due to a bad configuration value in the new chart version. You need to quickly restore the previously working state of the release. Which command achieves this most directly?

A platform engineer is authoring a new Helm chart and wants to inspect the exact Kubernetes manifests that would be produced from the templates and values — including any conditional blocks — before ever contacting the cluster or creating a release. Which Helm command best accomplishes this local rendering?