Top 30 Deployment Interview Questions and Answers

30 questions. Pick an answer, or open “Show the answer” to read it.

Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.

1. Question 1 of 30

   What is the significance of Vercel using the same public Adapter API contract as third-party platforms?

   • aThird-party platforms can achieve full framework fidelity without relying on reverse-engineered internals.
   • bAll platforms are required to use an identical runtime configuration generated by modifyConfig.
   • cVercel must submit adapter changes to the Ecosystem Working Group before deployment.
   • dVercel has open-sourced its adapter so platforms can replicate previously private build logic.
   Show the answer

   Answer: a · Third-party platforms can achieve full framework fidelity without relying on reverse-engineered internals.

   The correct answer is B because the card emphasizes that the public contract allows any platform to target the same framework fidelity as Vercel without reverse-engineering build output. Option D is tempting because Vercel did open-source its adapter, but the card explicitly states there are no private hooks, so there was no secret build logic to replicate.

   Read the full bite: Next.js 16.2 ships stable Adapter API for all platforms

2. Question 2 of 30

   How does Bitbucket prioritize the deployment status badge when a single commit maps to multiple environments with different states?

   • aIt shows all status badges side by side for every environment
   • bIt always shows the production environment's status first
   • cIt displays the status of the most recently deployed environment
   • dIt ranks statuses by urgency and surfaces the highest-priority state
   Show the answer

   Answer: d · It ranks statuses by urgency and surfaces the highest-priority state

   The card explains that badges bubble up by urgency, ranking Failed above Stopped, In Progress, and Successful. Distractor A is tempting because many tools sort by recency, but Bitbucket explicitly uses urgency-based prioritization.

   Read the full bite: Bitbucket beta adds live deployment status to PR lists

3. Question 3 of 30

   Which scenario would trigger an automated MLOps deployment but typically not a traditional DevOps pipeline?

   • aA scheduled rebuild of the serving application container
   • bProduction monitoring detecting drift in input data distributions
   • cA pull request merging changes to the model serving API
   • dA new GPU driver update pushed to the inference cluster
   Show the answer

   Answer: b · Production monitoring detecting drift in input data distributions

   The card states that MLOps deployments add triggers like data drift detection, unlike DevOps pipelines that react to code commits, dependency patches, or infrastructure changes. The GPU driver update is a tempting distractor because a common misconception is that MLOps is simply DevOps plus GPUs.

   Read the full bite: What are the primary differences between traditional DevOps and MLOps?

4. Question 4 of 30

   Which approach aligns with the 'build once, deploy many' principle when handling environment-specific database URLs?

   • aEmbed the database URL directly in the application binary during compilation for each target environment
   • bMaintain separate Git branches per environment and build from the branch matching the target deployment
   • cRebuild the image for each environment, passing the database URL as a build argument to the Dockerfile
   • dBuild the container image once, then provide the database URL via environment variables at deployment time
   Show the answer

   Answer: d · Build the container image once, then provide the database URL via environment variables at deployment time

   The correct answer preserves artifact immutability by externalizing configuration and deploying the same binary everywhere. Option C is tempting because build arguments appear to parameterize deployments cleanly, but they force per-environment rebuilds that can introduce unverified dependency changes.

   Read the full bite: What is a build artifact and why build once deploy many crucial?

5. Question 5 of 30

   A development team prioritizes rapid deployment of their custom web application and wants to avoid managing servers or operating systems. Which cloud service model best fits their needs?

   • aOn-premises hosting, to ensure maximum security and compliance by keeping everything in-house.
   • bPlatform as a Service (PaaS), as it abstracts away infrastructure, allowing focus on code and quick deployment.
   • cSoftware as a Service (SaaS), because it provides ready-to-use applications without any development effort.
   • dInfrastructure as a Service (IaaS), to retain full control over the underlying virtual machines and network.
   Show the answer

   Answer: b · Platform as a Service (PaaS), as it abstracts away infrastructure, allowing focus on code and quick deployment.

   PaaS is designed for rapid development and deployment by abstracting away the underlying infrastructure like servers and operating systems, allowing developers to focus solely on their application code. While IaaS offers control, it requires managing those underlying components, which the team wants to avoid.

   Read the full bite: Platform as a Service (PaaS): Focus on Code, Not Infrastructure

6. Question 6 of 30

   What is the primary advantage of implementing a Blue-Green deployment strategy?

   • aIt simplifies the process of performing backward-incompatible database schema changes.
   • bIt allows for efficient in-place upgrades on a single production environment without needing duplicates.
   • cIt significantly reduces the overall infrastructure costs for an application.
   • dIt ensures continuous service availability and provides immediate rollback capabilities during deployments.
   Show the answer

   Answer: d · It ensures continuous service availability and provides immediate rollback capabilities during deployments.

   The card states that Blue-Green deployment enables "zero-downtime releases and instant rollbacks," which directly translates to continuous service availability and immediate rollback. Option C is incorrect because this strategy temporarily doubles infrastructure costs.

   Read the full bite: Blue-Green Deployment: Zero-Downtime Releases

7. Question 7 of 30

   What is the primary distinguishing characteristic of CD4ML compared to traditional CI/CD pipelines?

   • aIt explicitly manages and automates changes across code, data, and trained models.
   • bIt guarantees that machine learning models will always outperform previous versions in production.
   • cIt focuses on automating the deployment of models to production without human intervention.
   • dIt reduces the need for data scientists by fully automating model development and training.
   Show the answer

   Answer: a · It explicitly manages and automates changes across code, data, and trained models.

   CD4ML's core innovation is extending CI/CD to manage the unique lifecycle of ML systems, which includes versioning and automating changes for code, data, and the trained model. While it does automate deployment (Option C), this is also a feature of traditional CI/CD; the distinction lies in the comprehensive management of data and models as first-class artifacts.

   Read the full bite: CD4ML: Automating ML from Data to Deployment

8. Question 8 of 30

   When is it most appropriate to use Expo Application Services (EAS)?

   • aDuring the initial phase of development to quickly prototype UI components in Expo Go.
   • bFor managing project dependencies and installing native modules directly on your local machine.
   • cTo start a local development server and debug JavaScript code on a simulator or device.
   • dWhen preparing a production-ready build for app store submission or pushing over-the-air updates.
   Show the answer

   Answer: d · When preparing a production-ready build for app store submission or pushing over-the-air updates.

   EAS is designed for production workflows, handling cloud builds, app store submissions, and over-the-air updates for React Native apps. It is explicitly stated as distinct from local development tools like the `expo` CLI, which are used for prototyping and running local development servers.

   Read the full bite: Expo Application Services (EAS): The Cloud Toolchain for React Native

9. Question 9 of 30

   Which characteristic of blue-green deployment most directly enables sub-minute rollback during a failed release?

   • aTraffic is shifted gradually to green while health metrics are monitored.
   • bGreen runs on the existing production instances alongside blue, separated by process or port isolation.
   • cThe blue environment remains fully operational and ready to receive traffic after cutover.
   • dDatabase schema changes are automatically rolled back by the orchestrator if green fails.
   Show the answer

   Answer: c · The blue environment remains fully operational and ready to receive traffic after cutover.

   The card states that because the old environment stays warm, rollback is a single traffic switch rather than a redeploy. Option A describes a canary release, which reuses the same infrastructure and gradually shifts traffic, making it a common misconception rather than true blue-green behavior.

   Read the full bite: Explain blue-green deployment, its prerequisites, and how it reduces deployment risk.

10. Question 10 of 30

    What is a key architectural difference between adapter-static and adapter-node?

    • aadapter-static pre-renders pages into HTML files at build time, whereas adapter-node produces a Node server for dynamic requests
    • badapter-static supports dynamic API routes and server hooks by default, whereas adapter-node only serves static files
    • cadapter-static bundles application code with Vite, whereas adapter-node relies on Rollup for bundling
    • dadapter-node generates static HTML for CDN hosts, whereas adapter-static requires a Node server on a VPS
    Show the answer

    Answer: a · adapter-static pre-renders pages into HTML files at build time, whereas adapter-node produces a Node server for dynamic requests

    adapter-static outputs static HTML for CDN deployment while adapter-node creates a running Node server capable of SSR and API routes. A is tempting but wrong because Vite handles bundling; an adapter only repackages the already-bundled output for a specific platform.

    Read the full bite: What is a SvelteKit adapter and how do adapter-static and adapter-node differ?

11. Question 11 of 30

    For what primary purpose is a SvelteKit adapter indispensable?

    • aTo translate the built application for a specific production hosting environment.
    • bTo integrate external APIs or databases into the application.
    • cTo enable server-side rendering for better search engine optimization.
    • dDuring local development to preview the final build output.
    Show the answer

    Answer: a · To translate the built application for a specific production hosting environment.

    SvelteKit adapters are essential for bridging the gap between SvelteKit's platform-agnostic build and the specific requirements of a production hosting environment. The card explicitly states that adapters are not needed during local development, as the vite dev server handles everything.

    Read the full bite: SvelteKit Adapters: Bridge Your App to Production

12. Question 12 of 30

    What is the primary benefit of using Uvicorn workers for a FastAPI application in production?

    • aIt automatically resolves performance issues caused by blocking I/O operations.
    • bIt simplifies debugging by providing clearer error tracebacks.
    • cIt enables automatic code reloading when changes are detected.
    • dIt allows the application to utilize multiple CPU cores for concurrent request processing.
    Show the answer

    Answer: d · It allows the application to utilize multiple CPU cores for concurrent request processing.

    Uvicorn workers are designed to scale your application by running multiple processes, each capable of handling requests, thereby utilizing all available CPU cores to process requests concurrently. Options A and B are incorrect because workers actually complicate debugging and disable auto-reloading; option A is wrong as workers do not fix fundamentally slow or blocking application logic.

    Read the full bite: Uvicorn Workers: Scaling Your FastAPI App

13. Question 13 of 30

    What type of content is explicitly advised AGAINST including directly within a build artifact?

    • aThe final, self-contained package for deployment
    • bThe fully compiled and linked executable files
    • cEnvironment-specific configuration variables or secrets
    • dThe zipped 'dist' folder of a web application
    Show the answer

    Answer: c · Environment-specific configuration variables or secrets

    The card explicitly states, "Do not bundle environment-specific configuration or secrets into an artifact." This ensures the artifact remains a generic, deployable unit, with configuration supplied at runtime. The other options describe components that are typically part of a build artifact.

    Read the full bite: Build Artifact: The Packaged Output of a CI Run

14. Question 14 of 30

    In an automated rollback pipeline triggered by a failed canary smoke test, which step must occur before redeploying the last known good release?

    • aPage the on-call engineer and wait for manual approval to proceed
    • bRun smoke tests against the previous release to confirm it is still healthy
    • cShift traffic back to the stable baseline and freeze the canary progression
    • dMutate the failed canary containers in place to patch the failing test
    Show the answer

    Answer: c · Shift traffic back to the stable baseline and freeze the canary progression

    The card states that traffic isolation—freezing the canary and shifting traffic to the stable baseline—must happen before any rollback begins to minimize blast radius. Running health checks against the previous release is part of post-redeploy verification, while manual approval or in-place patches break the automated safety contract.

    Read the full bite: Smoke test fails after canary deployment. Design the automated rollback.

15. Question 15 of 30

    What should an automated pipeline validate after a model is tagged Staging but before it receives production traffic?

    • aThat the registry label is updated to Production, which immediately routes 100% of traffic to the model
    • bThat training holdout metrics meet thresholds and the model card has been signed off
    • cData drift, performance regression, bias thresholds, schema compatibility, and security scanning
    • dThat the model owner approved the promotion via email and moved the registry tag to Production
    Show the answer

    Answer: c · Data drift, performance regression, bias thresholds, schema compatibility, and security scanning

    Before any traffic exposure, the pipeline must automatically validate data drift, performance regression, bias, schema compatibility, and security against production baselines. Option B is tempting because it mentions holdout metrics and model cards, but a signed card is a trigger rather than a validation gate, and holdout metrics alone omit critical production-specific checks like drift and bias.

    Read the full bite: Design a CI/CD pipeline that automates model promotion from Staging to Production

16. Question 16 of 30

    What is the core problem with deploying app:latest to production Kubernetes?

    • aKubernetes cannot pull images tagged latest
    • blatest images are always larger on disk
    • clatest disables health checks
    • dThe tag is mutable, so the same reference can resolve to different code across pods and time
    Show the answer

    Answer: d · The tag is mutable, so the same reference can resolve to different code across pods and time

    latest is a movable pointer, breaking reproducibility and rollbacks. It is not blocked by Kubernetes (A), unrelated to size (B), and does not affect health checks (C).

    Read the full bite: Why :latest is a production anti-pattern

17. Question 17 of 30

    Why is a Service needed in front of the Deployment's Pods for external access?

    • aA Service makes the image smaller
    • bPods cannot run web servers without one
    • cPod IPs are ephemeral, so a Service provides a stable endpoint and load-balances across them
    • dWithout it, the Deployment will not create Pods
    Show the answer

    Answer: c · Pod IPs are ephemeral, so a Service provides a stable endpoint and load-balances across them

    Pods get new IPs when rescheduled; a Service gives a durable virtual IP and balances traffic across current healthy Pods. The Deployment creates Pods regardless of any Service.

    Read the full bite: Minimal objects to expose a stateless app

18. Question 18 of 30

    Why is a StatefulSet, not a Deployment, the right choice for a clustered database?

    • aStatefulSets use less memory per Pod
    • bDeployments cannot mount any volumes
    • cEach Pod needs a stable identity and its own persistent volume that survives rescheduling
    • dStatefulSets always run faster than Deployments
    Show the answer

    Answer: c · Each Pod needs a stable identity and its own persistent volume that survives rescheduling

    A StatefulSet gives stable ordinal names, stable DNS, and per-Pod persistent storage that databases require. Deployments treat Pods as interchangeable and can mount volumes (B) but not per-Pod stable ones.

    Read the full bite: Deployment versus StatefulSet

19. Question 19 of 30

    During a Deployment image update, what mechanism actually performs the rolling update?

    • aEach Pod updates its own container image
    • bThe ReplicaSet rewrites its own Pods in place
    • cThe Deployment creates a new ReplicaSet and scales it up while scaling the old one down
    • dThe scheduler swaps the image on running Pods
    Show the answer

    Answer: c · The Deployment creates a new ReplicaSet and scales it up while scaling the old one down

    The Deployment orchestrates rollouts by creating a new ReplicaSet and shifting replicas between old and new. A ReplicaSet only maintains count; it does not rewrite Pods in place (B).

    Read the full bite: Deployment, ReplicaSet, and Pod hierarchy

20. Question 20 of 30

    After running kubectl create deployment webapp --image=my-app:1.0 with no extra flags, how many Pods does Kubernetes schedule by default?

    • aOne, because create defaults to a single replica
    • bAs many as there are worker nodes
    • cZero until you run kubectl apply
    • dThree, matching a typical production default
    Show the answer

    Answer: a · One, because create defaults to a single replica

    create deployment defaults to a single replica, so you must scale to reach three. The 'three by default' option is a common misconception; there is no automatic per-node or zero-replica behavior.

    Read the full bite: Create a Deployment with 3 replicas via kubectl

21. Question 21 of 30

    Which combination of automated CI tests best validates a classification model artifact before deployment?

    • aEnd-to-end tests confirming the training script finishes and the inference API returns predictions within 50 milliseconds
    • bHTTP endpoint tests, response latency checks, and load testing of the serving container
    • cData schema checks, performance regression against a baseline, bias audits, and artifact integrity tests
    • dUnit tests for the training code, code coverage thresholds, and pipeline linting
    Show the answer

    Answer: c · Data schema checks, performance regression against a baseline, bias audits, and artifact integrity tests

    Data schema checks, performance regression, bias audits, and artifact integrity tests validate the model artifact itself rather than just the surrounding code. Option A is tempting because it verifies the pipeline runs and responds quickly, but it never asserts whether the model's accuracy, fairness, or data assumptions have degraded.

    Read the full bite: What automated tests belong in CI before deploying a classification model?

22. Question 22 of 30

    In a CI/CD4ML pipeline, why is a model registry considered an active control plane rather than passive storage?

    • aIt provides a temporary staging area that holds the latest trained model between the CI training job and the CD deployment step.
    • bIt serves as a versioned artifact store where CI publishes validated models and CD consumes approved versions, enabling promotion workflows and rollback by switching version pointers.
    • cIt replaces experiment tracking tools by storing training parameters and metrics for every research run.
    • dIt acts as a cloud storage bucket for data scientists to manually upload model binaries, which engineers later copy into production.
    Show the answer

    Answer: b · It serves as a versioned artifact store where CI publishes validated models and CD consumes approved versions, enabling promotion workflows and rollback by switching version pointers.

    The registry is an active control plane because CI publishes validated, versioned artifacts with metadata and CD consumes approved versions, supporting promotion and rollback. Treating it as a manual cloud storage bucket misses the versioning, governance, and automated lifecycle contracts between data science and engineering.

    Read the full bite: What is a model registry's purpose in CI/CD4ML and its CI/CD interaction?

23. Question 23 of 30

    During a rolling update triggered by an image change, what does the Deployment controller actually do with the old ReplicaSet?

    • aMerges it into the new ReplicaSet
    • bDeletes it immediately to free resources
    • cEdits its Pods in place to use the new image
    • dScales it down gradually and retains it at zero for rollback
    Show the answer

    Answer: d · Scales it down gradually and retains it at zero for rollback

    The old ReplicaSet is scaled down progressively and kept at zero so rollout undo can restore it. Pods are never edited in place, and the old ReplicaSet is not deleted right away.

    Read the full bite: How a Deployment rolling update works

24. Question 24 of 30

    When you run kubectl rollout undo, how does Kubernetes restore the previous version so quickly?

    • aIt restores a snapshot of the Pods and their data
    • bIt scales the previously retained ReplicaSet back up and the bad one down
    • cIt re-pulls and rebuilds the old container image
    • dIt reschedules every Pod onto different nodes
    Show the answer

    Answer: b · It scales the previously retained ReplicaSet back up and the bad one down

    The old ReplicaSet was kept at zero, so undo just scales it up again. Rollback does not rebuild images or restore data; it only changes the workload's pod template back.

    Read the full bite: Rolling back a bad Deployment

25. Question 25 of 30

    Which sequence of quality gates correctly reflects the flow of the immutable container image toward production?

    • aBuild and unit tests, vulnerability scan, staging integration tests, canary with SLO checks
    • bVulnerability scan, build and unit tests, staging integration tests, canary with SLO checks
    • cBuild and unit tests, registry push, vulnerability scan, full production rollout
    • dBuild and unit tests, staging integration tests, vulnerability scan, production smoke tests
    Show the answer

    Answer: a · Build and unit tests, vulnerability scan, staging integration tests, canary with SLO checks

    The card describes a pipeline where the image is built and unit-tested first, scanned for vulnerabilities before registry push, validated in staging with integration tests, and finally promoted via canary using SLO checks. Option B reverses build and scan, C places staging before the security gate, and D pushes the image before scanning and skips the canary stage.

    Read the full bite: Describe essential CI/CD stages for a containerized app and critical quality gates

26. Question 26 of 30

    What does progressDeadlineSeconds do when new Pods in a rolling update never become Ready?

    • aIt forces the old Pods to be deleted to make room
    • bIt restarts each failing Pod after the deadline
    • cIt automatically rolls the Deployment back to the prior version
    • dIt marks the Deployment as failed (ProgressDeadlineExceeded) after that much time without progress
    Show the answer

    Answer: d · It marks the Deployment as failed (ProgressDeadlineExceeded) after that much time without progress

    After no progress for that duration, the controller sets the Progressing condition to False with reason ProgressDeadlineExceeded. It does not auto-rollback, delete old Pods, or restart the failing ones.

    Read the full bite: Stalled rollouts and progressDeadlineSeconds

27. Question 27 of 30

    Why is contract testing especially important in a microservice-based ML system?

    • aIt eliminates the need for API versioning
    • bIt replaces the need for any unit tests in each service
    • cIt allows all services to be deployed as a single unit
    • dServices evolve independently, so verifying interface and data-schema expectations catches breaking changes before integration
    Show the answer

    Answer: d · Services evolve independently, so verifying interface and data-schema expectations catches breaking changes before integration

    Independent release cadences make interface and schema drift the main risk; consumer-driven contract tests catch breaks in the producer's pipeline early. It complements, not replaces, unit tests and versioning.

    Read the full bite: CI/CD for microservice-based ML systems

28. Question 28 of 30

    On a git-based PaaS like Heroku, what is the role of the Procfile versus requirements.txt?

    • aThe Procfile stores secret config values for the running app
    • bBoth files list dependencies and one is just a backup of the other
    • crequirements.txt declares the start command; the Procfile lists Python packages
    • dThe Procfile declares the process start command; requirements.txt lists the dependencies to install
    Show the answer

    Answer: d · The Procfile declares the process start command; requirements.txt lists the dependencies to install

    requirements.txt tells the buildpack which packages to install, while the Procfile declares how to start each process, such as the web command. Secrets belong in config vars, not the Procfile.

    Read the full bite: Deploying to Heroku via Git

29. Question 29 of 30

    For which scenario is the Kubernetes Recreate deployment strategy the most appropriate choice?

    • aIntroducing a new database schema that is incompatible with the existing application version.
    • bEnsuring that users experience no service interruption during the update process.
    • cDeploying a critical, user-facing service that requires continuous availability.
    • dGradually updating an application to minimize the impact of potential bugs.
    Show the answer

    Answer: a · Introducing a new database schema that is incompatible with the existing application version.

    Option A is correct because the Recreate strategy is specifically designed for updates with breaking changes, such as database schema migrations, where old and new versions cannot coexist. Option B is incorrect because the Recreate strategy explicitly guarantees downtime, making it unsuitable for scenarios requiring no service interruption.

    Read the full bite: Recreate Deployment: Downtime for a Clean Slate

30. Question 30 of 30

    What is the primary role of a container registry in a build-and-deploy pipeline for Cloud Run?

    • aIt compiles the source code into a Docker image during the deploy stage
    • bIt runs the application's unit tests before the image is built
    • cIt stores the built, tagged image so the deploy stage can pull that exact artifact
    • dIt generates the Dockerfile automatically from the source repository
    Show the answer

    Answer: c · It stores the built, tagged image so the deploy stage can pull that exact artifact

    The registry stores immutable tagged images and is the handoff between build (which pushes) and deploy (which pulls). It does not compile code, run tests, or generate Dockerfiles.

    Read the full bite: CI/CD pipeline for a container PaaS