Operating Systems practice questions

Enable Legacy Boot (CSM)

Why wrong: Enabling Legacy Boot, also known as Compatibility Support Module (CSM), allows the UEFI firmware to emulate a traditional BIOS environment. This permits booting from older operating systems and bootloaders that do not support UEFI or Secure Boot, often lacking digital signature verification. Consequently, CSM would permit the execution of unsigned boot code, directly contravening any security policy requiring bootloader signature validation.

Enable TPM

Why wrong: Enabling the Trusted Platform Module (TPM) provides hardware-based security features such as cryptographic key generation, storage, and platform integrity measurements. While TPM can be used in conjunction with Secure Boot for advanced features like BitLocker drive encryption and remote attestation, its primary function is not to directly verify the digital signatures of bootloaders. TPM ensures the integrity of the system state after the bootloader has loaded, rather than enforcing the signature validation during the boot process itself.

Set boot order to network first

Why wrong: Setting the boot order to network first merely dictates the sequence in which the system attempts to load an operating system from various storage devices or network sources. While it can be useful for network installations or diskless workstations, modifying the boot order does not implement or enforce any security policies regarding the digital signatures of bootloaders. The system would still attempt to boot whatever it finds first in the specified order, regardless of its signature status, unless Secure Boot is also enabled.

Enable Fast Boot

Why wrong: Enabling Fast Boot primarily optimizes the boot process by skipping certain hardware initialization steps or resuming from a hibernation state, rather than performing a full cold boot. While this feature reduces startup time, it offers no mechanism for verifying the digital signatures of bootloaders or operating system components. Therefore, it fails to enhance system security against malicious code during the critical startup phase.

Enable Legacy Boot

Why wrong: Enabling Legacy Boot, also known as Compatibility Support Module (CSM), allows the system to boot using traditional BIOS-style methods, which predates and bypasses the UEFI Secure Boot process. This configuration explicitly permits the execution of bootloaders and operating systems that are not digitally signed or verified. Consequently, it introduces a significant security vulnerability by allowing potentially malicious or unauthorized code to run at startup.

Enable Boot from USB

Why wrong: Enabling "Boot from USB" merely configures the system's boot order to prioritize a USB device as a potential startup source, which is useful for installing operating systems or running diagnostic tools. This setting does not implement any security verification mechanisms for the boot process itself. It does not prevent unauthorized code from executing if a malicious USB drive is used, as it is solely a boot source selection, not a security feature.

The laptop's display cable has become disconnected

Why wrong: A disconnected display cable would result in a blank screen, meaning no image is transmitted to the laptop's display panel. However, this issue typically occurs *after* the Power-On Self-Test (POST) has completed successfully, or at least progressed past the initial hardware checks. The presence of beep codes indicates a fundamental hardware failure detected *during* POST, preventing the system from even reaching the point where it would attempt to output video, making a simple display cable disconnection an unlikely cause for diagnostic beeps.

The laptop's CMOS battery is dead

Why wrong: A dead CMOS battery primarily affects the system's ability to retain BIOS settings, such as the date, time, and boot order, when the laptop is powered off. While it can cause boot issues if critical settings are lost or revert to defaults, it generally does not trigger specific Power-On Self-Test (POST) beep codes. POST beep codes are reserved for critical hardware failures that prevent the system from initializing essential components like the CPU, RAM, or graphics, which are distinct from the function of the CMOS battery.

The user accidentally damaged the motherboard when installing the RAM

Why wrong: While it is certainly possible for a user to accidentally damage the motherboard during a RAM installation, such as by applying excessive force or causing an electrostatic discharge, a specific beep code typically points to a *diagnostic* failure rather than general, catastrophic physical damage. Beep codes are designed to pinpoint specific component failures, like incompatible or improperly seated RAM. General physical damage might result in no power, no POST, or erratic behavior, but a distinct beep pattern often indicates the system is still capable of performing basic diagnostics and identifying a particular hardware issue.

The RAID array was not properly initialized in the UEFI RAID utility.

Why wrong: If the RAID array was not properly initialized in the UEFI RAID utility, the configuration process itself would likely have failed, or the array would not present itself as a usable logical volume at all. Since the technician successfully configured the array, it implies that the necessary initialization steps were completed within the UEFI. The issue described, where the OS installer cannot find the volume, points to a problem with the operating system's ability to communicate with the *already configured* array, rather than the array's internal readiness.

The SATA mode is set to AHCI instead of RAID in the UEFI.

Why wrong: If the SATA mode were set to AHCI, the RAID utility would likely not be available to configure the array. Since the technician successfully configured the array, the SATA mode must have been set to RAID.

The UEFI boot mode is set to Legacy, which does not support RAID.

Why wrong: Setting the UEFI boot mode to Legacy primarily affects how the operating system is launched from a storage device, specifically whether it uses the older BIOS-style boot process or the newer UEFI method. This setting does not disable or interfere with the functionality of the RAID controller itself, nor does it prevent the OS installer from recognizing a RAID volume. The RAID array is configured and managed by the controller firmware, independent of the system's boot mode, and would still be visible to an OS installer equipped with the correct drivers.

The ISO file is corrupted

Why wrong: A corrupted ISO file would typically lead to errors during the loading of the operating system installer or boot environment itself, such as 'checksum mismatch' or 'read error' messages. The VM would attempt to access the ISO, but fail to properly execute the boot instructions contained within it, rather than reporting that no operating system was found on any device. This type of error indicates a problem with the *content* of the boot medium, not its absence or the inability to locate it.

The VM has insufficient RAM

Why wrong: Insufficient RAM would primarily manifest as a failure for the operating system to fully load or operate stably once it begins to boot, often resulting in a system crash, freeze, or extremely slow performance. The VM's firmware would still successfully identify and attempt to boot from a valid storage device containing an OS. The 'Operating system not found' error specifically indicates an inability to locate *any* bootable OS on the configured devices, not a resource limitation during OS execution.

The virtual hard disk is not attached

Why wrong: If the virtual hard disk is not attached to the VM, the virtual BIOS/UEFI would simply skip that device during the boot sequence. The VM would then proceed to attempt booting from the next device in the configured boot order, such as a virtual CD/DVD drive with an attached ISO. An 'Operating system not found' error would only occur if *no* bootable device, including any attached ISOs, was found throughout the entire boot sequence after exhausting all options in the boot order.

Enter the UEFI setup and change the boot order permanently.

Why wrong: Entering the UEFI setup utility to permanently alter the boot order is a functional, but inefficient, method for a one-time boot from a USB drive. This approach requires navigating through several menus to change the default boot sequence, and then necessitates re-entering the UEFI settings again later to revert the change to the original primary boot device, such as the internal hard drive. This makes it a cumbersome solution for a temporary need, as it modifies the system's persistent configuration unnecessarily.

Disable Secure Boot in the UEFI settings.

Why wrong: Disabling Secure Boot in the UEFI settings is unrelated to the process of selecting a different boot device. Secure Boot is a security feature designed to prevent unauthorized operating systems or malicious software from loading during the startup process by verifying the digital signatures of boot loaders. While it might be necessary to disable Secure Boot if the USB drive contains an unsigned or incompatible operating system, it does not influence the *order* in which bootable devices are presented or selected; its function is purely for boot integrity validation.

Remove all other bootable drives from the system.

Why wrong: Physically removing all other bootable drives from the system is an extreme, impractical, and entirely unnecessary measure for booting from a USB drive. This process involves opening the laptop chassis, disconnecting internal storage devices like SSDs or HDDs, and then reassembling the system, which is time-consuming and carries a risk of damaging components. Modern UEFI/BIOS firmware provides convenient software-based boot selection options, rendering such invasive hardware manipulation completely obsolete for this task.

One of the RAM modules is faulty and not being recognized by Windows.

Why wrong: If a RAM module were truly faulty, the system's Power-On Self-Test (POST) performed by the BIOS/UEFI firmware would likely detect the issue during boot-up. This would typically result in a system that either fails to boot entirely, displays specific error codes, or reports a lower *total* amount of installed RAM (e.g., 8GB total) in the BIOS and subsequently to Windows, rather than showing 16GB installed with only 8GB usable. Windows reports the memory quantity that the BIOS makes available.

The system is using a 32-bit version of Windows, which has a 4 GB limit.

Why wrong: A 32-bit operating system is inherently limited to addressing approximately 4 GB of physical memory due to its 32-bit memory addressing scheme. Even if 16 GB of RAM is physically installed, a 32-bit version of Windows would only recognize and make available up to 4 GB (often reported as 3.x GB usable). The symptom of 8 GB usable directly contradicts this fundamental architectural limitation of 32-bit systems.

Windows has a memory leak that is using 8 GB of RAM.

Why wrong: A memory leak occurs when an application or the operating system fails to release memory that it no longer needs, leading to a gradual increase in RAM consumption. While a severe memory leak could consume a significant amount of RAM, it would manifest as high *utilization* of the *total recognized* memory (e.g., 16 GB installed, 14 GB in use), not a reduction in the *total amount of RAM reported as available* to the operating system. The system would still report 16GB installed, but usage would be high.

The USB cable is too long

Why wrong: USB specifications define maximum cable lengths to ensure signal integrity, especially critical for USB 3.0's higher frequencies. Exceeding these limits leads to significant signal degradation, attenuation, and increased electromagnetic interference. This typically results in intermittent connection drops, data corruption, or complete device non-recognition, rather than a stable, consistent downgrade to a lower speed standard like USB 2.0. The system would struggle to maintain any reliable connection.

The front panel USB 3.0 header is loose

Why wrong: A loose connection at the internal USB 3.0 header on the motherboard means that the electrical contacts are not consistently making proper connection. This physical instability would manifest as devices intermittently connecting and disconnecting, or failing to be recognized at all, due to unreliable power or data lines. It would not cause a consistent, stable operation at a reduced speed, as the issue is one of physical contact rather than a protocol or driver limitation.

The motherboard's USB 3.0 controller is faulty

Why wrong: A hardware fault within the motherboard's integrated USB 3.0 controller typically results in a complete failure of the affected ports. This means devices connected would not be recognized, or the ports would be entirely inoperable, often accompanied by error messages in the Device Manager. It is highly unlikely for a faulty controller to consistently and stably operate at a lower speed (USB 2.0) without exhibiting other severe symptoms or complete failure, as the underlying hardware responsible for the higher speed protocol is compromised.

The fax line is plugged into the wrong port on the MFP.

Why wrong: If the fax line were plugged into the wrong port on the Multifunction Printer (MFP), neither incoming nor outgoing faxes would typically function. The physical connection is fundamental for any fax communication. Since outgoing faxes are working, it indicates the physical line connection to the appropriate fax port on the MFP is correctly established, making this an unlikely cause for only incoming fax failures.

The MFP's fax memory is full.

Why wrong: A full fax memory on the MFP would prevent the device from storing any new fax data, regardless of direction. This would manifest as failures for both incoming faxes, as there's no space to buffer them, and potentially outgoing faxes if the MFP needs to spool them before transmission. Since only incoming faxes are failing, the MFP's memory capacity is not the root cause.

The MFP's firmware is outdated.

Why wrong: Outdated firmware on a Multifunction Printer (MFP) can indeed lead to a range of operational problems, including general instability, compatibility issues, or specific feature malfunctions. However, it is less likely to cause a highly specific failure mode where only incoming faxes consistently fail while outgoing faxes work perfectly. Such a precise symptom strongly suggests a protocol-level incompatibility or misconfiguration within the VoIP system rather than a broad firmware defect affecting only one direction of a specific function.

Infrastructure as a Service (IaaS)

Why wrong: Infrastructure as a Service (IaaS) provides fundamental computing resources such as virtual machines, storage, and networking components over the internet. While it offers significant flexibility and control, the customer remains fully responsible for installing, configuring, and managing the operating system, middleware, runtime environments, and the application itself, including all necessary patching and security updates for those layers. This model would require the technician to handle OS and platform patching, which contradicts the implied need for a managed platform.

Software as a Service (SaaS)

Why wrong: Software as a Service (SaaS) delivers a complete, ready-to-use application directly to end-users over the internet, typically on a subscription basis. The entire application stack, from infrastructure to the application itself, is managed by the cloud provider, and users simply access the software via a web browser or client application. This model is designed for consuming a finished product, not for deploying custom applications or providing a platform for development, as the customer has no control over the underlying platform.

Desktop as a Service (DaaS)

Why wrong: Desktop as a Service (DaaS) provides virtualized desktop environments to end-users, accessible from various devices and locations. Its primary purpose is to deliver a consistent, secure, and centrally managed workspace for users, centralizing desktop management and reducing hardware costs. DaaS is entirely focused on user productivity and desktop delivery, making it irrelevant for deploying server-side cloud-based applications or providing a development platform.

Software as a Service (SaaS)

Why wrong: Software as a Service (SaaS) delivers fully functional, ready-to-use applications over the internet, managed entirely by the service provider. Users access these applications via a web browser or client interface without needing to install, maintain, or manage any underlying infrastructure, operating systems, or even the application software itself. This model is focused on consumption of a complete product, not on providing the environment to build or host custom solutions or manage an OS.

Platform as a Service (PaaS)

Why wrong: Platform as a Service (PaaS) provides a complete cloud-based environment for developing, running, and managing applications. It abstracts away the complexities of the underlying infrastructure, including operating systems, server hardware, and network configuration, allowing developers to focus solely on writing and deploying their application code and data. Users have control over their applications and some configuration settings but do not have administrative access or control over the host operating system.

Desktop as a Service (DaaS)

Why wrong: Desktop as a Service (DaaS) delivers virtualized desktop environments to end-users over a network, typically for individual productivity and application access. While it provides a complete desktop experience, DaaS is specifically designed for user workstations and application delivery, not for hosting server-side file shares or providing administrative control over a server's operating system. It focuses on user access to a personalized desktop, not on managing server infrastructure.

22

Why wrong: Port 22 is the standard for Secure Shell (SSH), a cryptographic network protocol used for secure remote command-line access, secure file transfers (SFTP), and tunneling services. Unlike RDP, SSH provides a text-based interface and is primarily used for managing servers and network devices, not for a full graphical desktop experience on Windows operating systems.

23

Why wrong: Port 23 is designated for Telnet, an older network protocol used for unencrypted command-line communication with remote devices. Its significant security vulnerability, due to transmitting data including credentials in plain text, makes it unsuitable for modern secure remote access needs and certainly not for providing a graphical Windows Remote Desktop session.

5900

Why wrong: Port 5900 is commonly associated with Virtual Network Computing (VNC), a cross-platform desktop sharing system that allows users to remotely control another computer's graphical interface. While VNC provides similar functionality to RDP in offering a remote graphical desktop, it operates using a different protocol and client software, making it distinct from the specific RDP service.

802.11ac

Why wrong: 802.11ac, also known as Wi-Fi 5, primarily utilizes the 5 GHz frequency band. While offering higher theoretical throughput, this band is inherently more susceptible to signal attenuation over distance and struggles significantly with penetration through common building materials such as concrete, metal, and even drywall. This characteristic makes 802.11ac a poor choice for environments requiring extensive coverage and obstacle penetration, like a large warehouse.

802.11n

Why wrong: 802.11n, known as Wi-Fi 4, is a dual-band standard capable of operating on both 2.4 GHz and 5 GHz frequencies. Crucially, its 2.4 GHz operation offers significantly better signal propagation and penetration through walls and other obstacles compared to 5 GHz bands. This characteristic makes 802.11n an excellent choice for environments like warehouses where long-range coverage and reliable signal penetration through various materials are paramount, balancing performance with robust connectivity.

802.11a

Why wrong: 802.11a is an older wireless standard that exclusively operates within the 5 GHz frequency band. Due to the inherent physical properties of 5 GHz signals, 802.11a suffers from limited range and notably poor penetration capabilities through common building materials. This makes it highly impractical for any environment requiring extensive coverage or reliable connectivity through obstacles, rendering it entirely unsuitable for a new wireless network setup in a challenging physical space.

The CPU is counterfeit and only has two functional cores

Why wrong: A counterfeit CPU, while a possibility, is an uncommon cause for only a partial core count being reported. Such a CPU would more typically lead to severe system instability, boot failures, or incorrect CPU model identification rather than merely detecting fewer functional cores. The system would likely exhibit more critical symptoms if the CPU itself were compromised or physically damaged in a way that disabled specific cores.

The operating system is limited to two cores due to licensing

Why wrong: Operating system licensing, particularly for consumer versions like Windows Home or Pro, typically limits the number of physical CPU sockets a system can utilize (e.g., one), but it does not restrict the number of cores visible or usable within that single CPU. All cores on a properly installed and supported CPU should be detected and reported by the operating system, even if other OS features or performance are limited. Therefore, missing cores are not a licensing issue.

The CPU cooler is too tight, causing physical damage to the CPU

Why wrong: An overtightened CPU cooler typically causes significant physical stress to the CPU package or the motherboard socket. This type of damage would most likely result in catastrophic system failures, such as the system failing to POST, immediate shutdowns, or severe instability and crashes. It is highly improbable that an overtightened cooler would selectively disable only a portion of the CPU cores while allowing the rest of the system to function normally.

The app is not compatible with the device's screen resolution.

Why wrong: Modern Android applications are typically designed with responsive layouts and utilize density-independent pixels (dp) to adapt to a wide range of screen sizes and resolutions. While an incompatible resolution might lead to display issues or a suboptimal user experience after installation, it rarely prevents the initial installation of an application from the Google Play Store. The Play Store primarily filters apps based on OS version, CPU architecture, and device features, not usually screen resolution as a hard blocker for installation.

The Google Play Store app needs to be reinstalled.

Why wrong: The Google Play Store is a deeply integrated system application on Android devices, and reinstalling it is an extremely rare and often complex procedure, typically requiring advanced troubleshooting steps like factory resets or flashing firmware. For a single application failing to install, issues are almost always specific to the app itself, the device's configuration, or network connectivity, rather than a fundamental corruption of the Play Store application itself. Reinstalling it would be an unwarranted and disproportionate first step.

The user is not signed into their Google account.

Why wrong: While a Google account is essential for accessing the Google Play Store and is required for purchasing paid applications or managing subscriptions, it is not strictly necessary to be signed in to download and install many free applications. Furthermore, if a user were not signed in, the Play Store would typically prompt them to sign in or create an account before attempting any download, rather than simply preventing an app from installing without explanation. The scenario does not indicate such a prompt.

A USB-C hub with Bluetooth functionality to extend range.

Why wrong: A USB-C hub primarily provides port expansion for a tablet. While some hubs may integrate a Bluetooth radio, this typically functions as an alternative Bluetooth controller rather than a range extender for the tablet's existing Bluetooth module. It would not inherently boost the signal strength or effective operational distance of the tablet's native Bluetooth connection, which is the primary need when seeking to extend range.

A Bluetooth adapter plugged into the tablet's charging port.

Why wrong: Plugging a Bluetooth adapter into a tablet's charging port (typically a USB-C or Micro-USB data/power port) is generally redundant for modern tablets, as most come equipped with integrated Bluetooth capabilities. Such an adapter would function as a separate Bluetooth controller, not as a signal booster for the tablet's internal radio. It is unlikely to significantly extend the operational range beyond the tablet's native Bluetooth, as its power output and antenna design are usually comparable.

A wireless dongle that connects both keyboard and mouse via a single receiver.

Why wrong: A wireless dongle that connects a keyboard and mouse via a single receiver typically utilizes a proprietary 2.4 GHz radio frequency, not standard Bluetooth. These dongles are designed for specific non-Bluetooth wireless peripherals from the same manufacturer and create a dedicated, closed connection. Since the customer explicitly wants to connect *Bluetooth* devices, this type of proprietary dongle is incompatible and unnecessary, as Bluetooth devices connect directly to a Bluetooth host without needing a proprietary receiver.

DHCP

Why wrong: DHCP (Dynamic Host Configuration Protocol) is incorrect because its primary function is to assign IP addresses and other network configuration parameters to clients, not to directly detect IP conflicts. While a DHCP server can be configured to perform conflict detection (e.g., by sending an ICMP ping or an ARP probe to a proposed IP address before offering it), DHCP itself is not the protocol that performs the detection. It relies on other network protocols to verify address availability, making it an indirect mechanism rather not the direct detection protocol.

ICMP

Why wrong: ICMP (Internet Control Message Protocol) is incorrect because it is primarily used for error reporting and network diagnostics, such as the `ping` utility, which tests connectivity between hosts. While a device could theoretically ping its own assigned IP address to see if another device responds, this is not a standard or reliable method for detecting an IP conflict. ICMP does not directly reveal the MAC address of a conflicting device, nor does it inherently manage the mapping of IP to MAC addresses required for direct conflict identification.

DNS

Why wrong: DNS (Domain Name System) is incorrect because its fundamental role is to translate human-readable hostnames into numerical IP addresses, and vice-versa. DNS operates at the application layer and is entirely unrelated to the detection of duplicate IP addresses on a local network segment. It has no inherent mechanism to monitor for IP address conflicts or to report when two different devices are configured with the same IP address, as its database is for name resolution, not real-time network address management.

Spectrum analyzer

Why wrong: A spectrum analyzer measures radio frequency energy across a band, identifying interference sources like microwaves or Bluetooth, but it does not decode 802.11n channel utilisation or beacon frames to show which channel has the fewest active Wi-Fi clients. It is tempting because it visualises signal strength and noise, which seems relevant to congestion; however, it would be correct only when troubleshooting non-Wi-Fi interference, such as a cordless phone or radar, not for selecting a Wi-Fi channel based on client load.

Cable tester

Why wrong: A cable tester is a specialized diagnostic device used exclusively to verify the physical integrity and proper wiring of Ethernet cables, checking for issues such as continuity, open circuits, shorts, and miswires. While indispensable for troubleshooting wired network segments and ensuring proper Layer 1 connectivity, it possesses no capability to interact with, analyze, or provide any information about wireless network channels, signal strength, or RF interference. Therefore, a cable tester is entirely irrelevant for diagnosing or optimizing a wireless network's channel configuration.

Ping command

Why wrong: The `ping` command is a fundamental network utility designed to test the reachability of a host on an Internet Protocol (IP) network and to measure the round-trip time for messages. Operating at the network layer (Layer 3) of the OSI model, it confirms basic IP connectivity and latency between two devices. However, `ping` provides no insight into the underlying physical or data link layer issues, such as Wi-Fi channel utilization, signal-to-noise ratio, or co-channel interference, which are critical factors when selecting an optimal wireless channel.

Update the UEFI firmware to the latest version from the manufacturer.

Why wrong: Updating the UEFI firmware to the latest version from the manufacturer can introduce support for newer hardware or features, including potentially a TPM module if it wasn't previously recognized. However, a firmware update alone does not automatically enable the TPM; it merely provides the capability. The TPM must still be manually activated within the UEFI's security settings after the update is complete.

Disable the integrated graphics to free up resources for TPM.

Why wrong: Disabling integrated graphics to 'free up resources' for the Trusted Platform Module is incorrect because TPM operates as a distinct hardware component or a firmware module within the system's security architecture. Integrated graphics, conversely, is a separate processing unit dedicated to display output. These components do not share or compete for the same system resources in a manner where disabling one would benefit the other's functionality or availability.

Set the SATA controller to RAID mode.

Why wrong: Setting the SATA controller to RAID mode primarily configures how storage drives are managed, enabling features like data striping for performance or mirroring for redundancy across multiple disks. This setting, whether RAID, AHCI, or IDE, exclusively pertains to the storage subsystem's operation and has no functional relationship or impact on the Trusted Platform Module. TPM is a security chip or firmware module entirely separate from disk controller configurations.

Install a Type 2 hypervisor on each physical server

Why wrong: Installing a Type 2 hypervisor, such as Oracle VirtualBox or VMware Workstation, on each physical server would not achieve consolidation. These hypervisors run as an application within a host operating system, introducing significant overhead due to the additional OS layer. This architecture consumes more resources and offers reduced performance compared to bare-metal solutions, making it inefficient for consolidating multiple production servers onto fewer physical machines. Furthermore, it would still require five physical servers, defeating the purpose of consolidation.

Migrate all applications to a single OS using compatibility layers

Why wrong: Migrating all applications to a single operating system using compatibility layers, such as Wine for Linux or Windows' built-in compatibility modes, is not a viable solution for consolidating five physical servers that likely run diverse operating systems. Compatibility layers allow applications designed for one OS to *attempt* to run on another, but they do not provide the isolation or the ability to run distinct operating systems concurrently. This method would require extensive re-engineering, might introduce instability, and fails to address the fundamental need to host multiple, potentially different, server environments.

Use containerization instead of virtualization

Why wrong: While containerization, using technologies like Docker or Kubernetes, offers excellent application isolation and portability, it is fundamentally different from virtualization in this context. Containers share the host operating system's kernel, meaning all containers on a single host must run on the same underlying OS (e.g., Linux containers on a Linux host). This approach cannot consolidate five physical servers that are likely running different operating systems (e.g., Windows Server, various Linux distributions) into distinct, isolated environments, as each would require its own kernel, which containers do not provide.