Top 30 Easy DevOps & Cloud Concepts Quiz for Beginners
30 easy multiple-choice DevOps & Cloud concept questions, the vocabulary and first principles, the parts you need before anything else makes sense. They come from 30 bites in the DevOps & Cloud library, the gentlest slice of the 619 DevOps & Cloud concept questions in the library. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
Infrastructure, containers, CI/CD, and cloud
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.
Question 1 of 30
What is the core philosophy behind Site Reliability Engineering (SRE)?
Show the answer
Answer: b · To treat operational challenges as software problems that can be solved through engineering.
SRE's fundamental principle is to approach operations as a software problem, using engineering to automate and manage systems, as stated in the card. Option D is incorrect because SRE was developed as a new approach to overcome the limitations of traditional operations.
Read the full bite: Site Reliability Engineering (SRE): Ops as a Software Problem
Question 2 of 30
What problem does cloud computing primarily solve for businesses launching new digital services?
Show the answer
Answer: c · The high upfront costs and risks of owning physical IT infrastructure.
The card states cloud computing was created to solve "huge upfront capital costs, long procurement times, and the risk of buying too much or too little capacity" associated with owning physical servers. While cloud computing can help with IT personnel challenges (A) and high availability (D), these are not its primary foundational purpose.
Read the full bite: Cloud Computing: Renting Someone Else's Computer
Question 3 of 30
A developer needs to deploy a microservices application with minimal resource usage and fast startup times. Which technology is generally preferred and why?
Show the answer
Answer: a · Containers, because they share the host OS kernel, reducing overhead.
Containers are preferred for microservices due to their low overhead and fast startup times, achieved by sharing the host OS kernel. VMs, while offering strong isolation, incur significant resource overhead by emulating a full OS.
Read the full bite: VMs vs. Containers: Houses vs. Apartments
Question 4 of 30
Which characteristic is most crucial for an effective build automation process?
Show the answer
Answer: c · It consistently transforms source code into a runnable application, regardless of the environment.
The card emphasizes that build automation makes the process "repeatable, reliable" and ensures "the same result every time, no matter who pushes the 'start' button." Option C directly reflects this core benefit. Option D describes the "it works on my machine" problem that build automation aims to eliminate, not a desired characteristic.
Question 5 of 30
Which statement best describes a core benefit of adopting public cloud for a new business?
Show the answer
Answer: c · It enables rapid resource scaling and avoids large upfront capital investments.
Option C is correct because the card emphasizes public cloud's ability to turn rigid capital expense into flexible operational expense, allowing rapid scaling without large upfront hardware purchases. Option D is incorrect as the card notes that public cloud may not be cost-effective for stable, high-utilization workloads and uncontrolled usage can lead to higher costs.
Read the full bite: Public Cloud: Renting, Not Owning, Your Datacenter
Question 6 of 30
Which of the following best exemplifies 'toil' in an engineering context?
Show the answer
Answer: c · Manually running a script to provision resources for each new customer
Option C perfectly matches the definition of toil: it is manual, repetitive, automatable, tactical, provides no lasting value, and scales linearly with service growth. Option A, attending meetings, is explicitly categorized as 'overhead' rather than toil, as it doesn't scale with service load in the same way.
Read the full bite: Toil: The Repetitive Work That Kills Engineering Velocity
Question 7 of 30
What is Docker's primary method for resolving the 'Works on My Machine' problem?
Show the answer
Answer: a · It bundles the application with all its specific dependencies into a portable, consistent unit.
The card explicitly states Docker solves this by "packaging an application with all of its dependencies... into a single, isolated unit called a container image." This ensures the environment is consistent everywhere. While related to isolation, containers are distinct from full virtual machines, which are heavier and emulate entire hardware systems.
Question 8 of 30
What is the key feature that distinguishes a private cloud from a traditional, on-premises data center?
Show the answer
Answer: d · It offers on-demand, self-service access to resources through a management software layer.
A private cloud's defining characteristic is the cloud management software stack that provides self-service, on-demand access and automation, differentiating it from a traditional data center which may also own its hardware and use virtualization but lacks these cloud-like capabilities. While option B is often true for private clouds, it's also true for traditional data centers, so it's not the distinguishing factor.
Read the full bite: Private Cloud: Cloud Computing on Your Terms
Question 9 of 30
What is a key advantage of automated testing in modern software development?
Show the answer
Answer: a · It allows for rapid and confident deployment of code changes by detecting regressions early.
The card highlights that automated testing "provides the confidence needed to deploy changes frequently" and is "the foundation for catching regressions." Option B is incorrect because the card explicitly states automated testing is "not suited for exploratory testing... or for assessing subjective user experience."
Read the full bite: Automated Testing: Catch Bugs Before They Ship
Question 10 of 30
In an Infrastructure as a Service (IaaS) model, which aspect of the computing environment is the user primarily responsible for managing?
Show the answer
Answer: b · The operating system, applications, and data.
The card states that in IaaS, "you're still responsible for managing the OS and all software" and compares it to bringing your "OS, applications, and data." Option D describes a Platform as a Service (PaaS) or Serverless model, which IaaS is explicitly contrasted with for users who want to avoid server management.
Read the full bite: Infrastructure as a Service (IaaS): Renting the Data Center
Question 11 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?
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
Question 12 of 30
What is a key advantage of adopting a Software as a Service (SaaS) model?
Show the answer
Answer: c · Transferring the burden of software maintenance, hosting, and updates to the vendor.
SaaS shifts the responsibility for hosting, maintenance, and updates from the customer to the software provider, which is a primary advantage. While SaaS offers cost-effectiveness, it involves recurring subscription fees rather than eliminating all expenses.
Read the full bite: SaaS: Renting Software Instead of Owning It
Question 13 of 30
What is the main drawback of over-instrumenting an application with telemetry?
Show the answer
Answer: a · It creates excessive data, increasing storage costs and performance overhead.
The card explicitly states that over-instrumentation generates a 'massive volume of data that is expensive to store and process, and can even add performance overhead.' While too much data can make identification harder, the primary risk highlighted is the cost and performance impact.
Read the full bite: Code Instrumentation: Making Your App Observable
Question 14 of 30
What is the primary functional distinction between stopping a container and removing it?
Show the answer
Answer: d · Stopping a container allows it to be restarted later with its preserved internal state, whereas removing it permanently deletes the container instance and any data not on a volume.
The card explicitly states that stopping a container retains its state, allowing it to be restarted, while removing it permanently deletes the container and its non-volume data. Option A is incorrect because 'stop' sends a graceful shutdown signal (SIGTERM), not an immediate termination, and 'rm' deletes an already stopped container, it doesn't initiate the shutdown process itself.
Read the full bite: Container Lifecycle: From Create to Remove
Question 15 of 30
What is the primary purpose of a health check endpoint, distinguishing it from merely confirming a service process is running?
Show the answer
Answer: d · To allow external systems to detect if the service can perform its core functions and route traffic accordingly.
The card explicitly states that a health check answers 'Can you do your job?', enabling load balancers and orchestrators to stop routing traffic to sick instances. Options A and D are incorrect because health checks provide a binary signal, not detailed metrics or comprehensive logs. Option A is a distractor because while orchestrators may restart services based on health checks, the health check itself provides the signal of functional impairment, not the direct trigger for a restart based solely on resource thresholds.
Read the full bite: Health Checks: Is Your Service Alive or Just Running?
Question 16 of 30
Which core problem in software development does a Dockerfile primarily address?
Show the answer
Answer: c · Guaranteeing that an application's runtime environment is identical everywhere it runs.
The card explicitly states Dockerfiles exist "To solve the classic 'it works on my machine' problem" and "ensure that an application and its dependencies are packaged together and run consistently everywhere." This aligns perfectly with guaranteeing an identical runtime environment. While Docker is used in CI/CD (which includes testing automation), the Dockerfile's direct role is defining the environment, not the testing process itself.
Read the full bite: The Dockerfile: A Recipe for Your Container
Question 17 of 30
Which statement best describes a core operational principle of a Distributed Version Control System (DVCS)?
Show the answer
Answer: b · Each developer works with a complete, independent copy of the entire project history on their local machine.
A DVCS provides every developer with a full, independent copy of the entire repository and its history, allowing most operations to occur locally. Option D describes a centralized system, where commits are immediately synchronized with a single server.
Read the full bite: Distributed Version Control (DVCS): Everyone Gets a Copy
Question 18 of 30
What does a Git commit fundamentally represent?
Show the answer
Answer: c · A complete snapshot of all tracked files in the project at a specific point in time.
A Git commit is described as a 'permanent snapshot of your entire project,' containing the complete state of all tracked files. Option A is a common misconception, as Git stores full snapshots, not just diffs. Options C and D describe aspects of the commit process or metadata, not the core content of the commit itself.
Question 19 of 30
What is the primary reason to avoid using the "latest" tag for Docker images in production or CI/CD pipelines?
Show the answer
Answer: b · The image associated with the "latest" tag can be updated at any time, leading to non-reproducible builds and unexpected behavior.
The card explicitly states that the image 'latest' points to can change without warning, leading to unexpected failures or behavior drift, making builds non-reproducible. This mutability is the core issue, not that it's inherently unstable or automatically purged.
Read the full bite: Docker Image Tagging: Versioning for Containers
Question 20 of 30
You've committed a file to your Git repository. Later, you decide this file should not be tracked. What is the correct way to stop Git from tracking it using .gitignore?
Show the answer
Answer: c · Use git rm --cached <file> and then add the file's pattern to .gitignore.
The card states that .gitignore only works on untracked files. To stop tracking a file already committed, you must first remove it from the index using git rm --cached <file>, then add its pattern to .gitignore to prevent it from being tracked again. Simply adding it to .gitignore (option B) will not affect files already under version control.
Question 21 of 30
What is the primary reason Git's branching model is considered superior to older version control systems?
Show the answer
Answer: b · It allows for rapid creation of isolated development lines without duplicating the entire codebase.
The card states that Git branches are lightweight pointers, not full copies, making their creation and switching nearly instant. This contrasts with older VCS that often required heavy, full copies, which discouraged frequent branching. Option B directly captures this core advantage.
Read the full bite: Git Branch: A Lightweight Pointer, Not a Full Copy
Question 22 of 30
What is a key characteristic that distinguishes a Virtual Machine (VM) from simply running multiple applications on a single operating system?
Show the answer
Answer: d · VMs enable the execution of entirely separate operating systems on a single physical machine.
The core purpose of a VM is to run multiple isolated operating systems on a single physical machine, each with its own OS. Option B is incorrect because VMs do not share the host's OS kernel; that is a characteristic of containers.
Read the full bite: Virtual Machine (VM): A Computer Inside a Computer
Question 23 of 30
What is the primary benefit of using a machine image for deploying servers?
Show the answer
Answer: a · It enables rapid and consistent provisioning of identical virtual machines.
The card emphasizes that machine images solve "slow, error-prone, and inconsistent server provisioning" by acting as a "cookie cutter" to launch "hundreds of identical virtual machines" quickly. Option D is incorrect because images are for identical servers; unique configurations often require additional tools. Option C is incorrect as the card states images can be overkill for simple applications, where Docker might be preferred.
Read the full bite: Machine Images: The Blueprint for Your Servers
Question 24 of 30
Which scenario best illustrates the primary advantage of using cloud instances?
Show the answer
Answer: b · A website experiencing significant, unpredictable spikes in user traffic throughout the day.
Cloud instances are designed for elasticity, allowing users to scale computing resources up or down rapidly to meet fluctuating demand and pay only for the time they are active. A website with unpredictable traffic spikes directly benefits from this on-demand scalability, unlike scenarios with consistent loads or static needs.
Read the full bite: Cloud Instances: Renting Servers on Demand
Question 25 of 30
According to the error budget concept, when should a development team prioritize reliability work over shipping new features?
Show the answer
Answer: a · When the error budget is low or exhausted, indicating a risk to the SLO.
The card states that when the budget is low or exhausted, all non-essential changes are frozen to focus on reliability. Option B describes the opposite scenario, where a healthy budget allows for new features and experiments, not a shift to prioritizing reliability.
Read the full bite: Error Budgets: The Currency of Reliability
Question 26 of 30
What is the primary reason the card advises against using calendar months for SLO time windows?
Show the answer
Answer: b · Their varying lengths complicate consistent error budget calculations.
The card explicitly states that calendar months have 'unequal lengths and complicate budget math,' making a 1% error budget represent different amounts of downtime. This inconsistency makes it difficult to calculate and manage the error budget reliably. Option A is a general issue with long windows, not specific to calendar months' primary drawback.
Read the full bite: SLO Time Windows: Choosing Your Measurement Period
Question 27 of 30
What is the main limitation of using Docker Compose alone for production environments?
Show the answer
Answer: c · It lacks features for high availability and automatic scaling.
The card explicitly states that Docker Compose should not be used alone for production because it lacks high-availability, fault tolerance, load balancing, and auto-scaling. The other options describe functionalities that Docker Compose is designed to handle, such as defining multi-service applications, managing networks, and supporting persistent data via volumes.
Read the full bite: The docker-compose.yml File: Your App's Blueprint
Question 28 of 30
Which statement best describes the fundamental purpose of an SLO document?
Show the answer
Answer: c · To establish a formal, measurable agreement on a service's acceptable reliability, guiding engineering decisions.
The card defines an SLO document as a "formal contract" that specifies "measurable targets" for reliability, guiding "engineering priorities" and "data-driven decisions." Option C directly reflects this core purpose. The other options describe different types of documentation or tools, not an SLO document.
Read the full bite: SLO Document: Your Service's Reliability Contract
Question 29 of 30
What is the primary benefit of defining services in a Docker Compose file for an application?
Show the answer
Answer: c · It provides a declarative way to manage multiple interconnected containers as a single application.
The card states that Docker Compose's purpose is to "manage multi-container applications declaratively" and allows you to "spin up a complete, interconnected environment with a single command." Option A describes features of production orchestration tools like Kubernetes, which the card explicitly states Compose is not.
Read the full bite: Docker Compose Services: Defining Your App's Components
Question 30 of 30
For which scenario is Docker Compose most effectively utilized?
Show the answer
Answer: d · Orchestrating a multi-service application stack for local development and automated testing.
Docker Compose is explicitly designed for orchestrating multi-container applications in local development environments and for automated testing, simplifying the setup of complex service dependencies. It is not recommended for large-scale production deployments, which require more advanced cluster orchestrators.
Read the full bite: Docker Compose: Orchestrate Multi-Container Apps Locally
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.