Delivery & cloud interview practice.
Rehearse with explained interview questions. Describe the mechanism, trace an example, and explain a trade-off before revealing the answer.
How to use this session
- Choose a level and session length. Try each prompt before opening the notes.
- Compare your explanation with the source answer and revisit any concept you missed.
- Mark the questions you reviewed. Sign in to save session history; your draft answers stay in this page.
Code is provided for reading and tracing. These sessions do not execute or automatically grade code.
Delivery & cloud practice
Think first. Reveal second.
Explain your reasoning before opening the notes. A focused session lets you choose your question count; mock rounds follow the original guide.
1 questions match your selection.
Preview the Delivery & cloud question pool
- CI vs continuous delivery vs continuous deployment?
Continuous integration checks changes frequently through automated builds and tests. Continuous delivery keeps a verified release ready for deployment, while continuous deployment automatically sends qualifying changes to production. The distinction is the production release decision, not whether any automation exists.
- What should a pipeline do?
A delivery pipeline turns source changes into a verified, versioned artifact and releases it through controlled environments. Each step should provide evidence that the next step is safe and reproducible. Promoting the same artifact avoids rebuilding slightly different software for each environment.
- What are GitHub Actions concepts?
GitHub Actions defines automated workflows triggered by repository or scheduled events. Workflows contain jobs that run on runners, and jobs contain ordered steps using commands or reusable actions. Artifacts and outputs move results between steps or jobs, while permissions control what the workflow may access.