Cloud computing is about delivering computing resources—like servers, storage, databases, and software—over the Internet so you can access and use them without owning or managing the physical hardware. This setup lets you scale resources up or down as needed and pay only for what you use, from anywhere you have online access. Storing data on local hard drives only is limited to a single device or location and doesn’t provide the on-demand, scalable access that cloud services offer. Running all software on personal devices ignores the benefits of centralized, remotely hosted applications. Using only on-premises servers reflects traditional IT infrastructure rather than the internet-based delivery model that defines cloud computing.

During startup, firmware like BIOS or UEFI is the first software that runs. It performs a Power-On Self-Test to verify essential hardware, initializes components such as the CPU, memory, graphics, and storage controllers, and configures the basic environment the operating system needs. It then detects boot devices, follows the boot order, and starts the boot process by loading the operating system loader so the OS can take control. This stage is crucial because the OS cannot start until the hardware is ready and a proper boot path is established. In modern UEFI systems you might see features like Secure Boot and more advanced setup options, but the fundamental role is the same: prepare the hardware and hand control to the OS. The other statements don’t fit because firmware isn’t used to launch individual applications, store user documents, or act only after the OS has loaded.

Multi-factor authentication adds a second barrier to login beyond just a password. When you require something you have or something you are in addition to something you know, a thief who phishes for your password can’t complete the login on their own. Even if they copy or guess the password, they still need that second factor—like a code from an authenticator app or a hardware security key—which is much harder to obtain or reproduce. This dramatically reduces the risk of credential theft through phishing. Firewalls protect network boundaries, not the act of stealing credentials via a fake login page. Antivirus helps detect malware but doesn’t prevent a user from entering credentials on a phishing site. Backups guard data after a breach but don’t stop the attacker from obtaining credentials in the first place. Using a strong, phishing-resistant form of MFA (for example, a hardware key) provides even stronger protection, but the core idea is clear: requiring a second factor makes stolen passwords far less useful.

The part of a URL that jumps to a subsection within a resource is the fragment identifier, which comes after the hash symbol (#). This fragment points to a specific part of the document, such as an element with a matching id, so the browser can scroll directly to that section. For example, https://example.com/manual.html#getting-started will open the manual page and jump to the section labeled "getting-started." This is different from the scheme (http or https), which tells the browser how to fetch the resource, the path, which locates the resource on the server, and the query, which passes additional parameters to influence the resource’s response. The fragment is specifically for navigating to a place within the already-loaded document.