A multipartite virus infects both the boot sector and executable files, allowing it to spread through multiple infection methods simultaneously.

The objective is to conduct passive reconnaissance for potentially exposed administrative documents on .
onion sites, using advanced search operators. The query should therefore (1) restrict results to the hidden- network domain space, (2) focus on document formats likely to contain internal material, and (3) use a title
/header hint that aligns with management or administration content.
Option C is the best match because it combines:
site:onion to constrain results to .onion resources (the target environment of concern), filetype:pdf to focus on a common format for internal documents (policies, reports, procedures, administrative exports), and intitle: " admin access " to search for pages/files whose title/header metadata indicates administrative relevance. Using intitle aligns with the requirement to look for files "with headers suggesting management- related content," because titles are a practical proxy for document headers and indexing metadata.
By comparison, A does not include site:onion, so it is not scoped to hidden services, and it targets
"credentials" rather than administrative documents. B includes site:onion and filetype:pdf, but the title focus is "secure login," which is more likely to find authentication pages or generic security guidance rather than administrative document exposure. D is also plausible (docx + user accounts), but "user accounts" tends to point to account lists or HR-style docs rather than broader administrative access documentation, and PDFs are frequently used for formal administrative documentation and may be more commonly indexed.
Thus, C best satisfies the passive, targeted reconnaissance requirement for admin-related documents on .onion sites.

Static Network Address Translation (Static NAT) allows a single private IP address to be mapped to a single public IP address. This one-to-one mapping ensures that the same internal machine is always reachable through the same external IP address, which is crucial for "server publishing" - making internal servers (e.g., web servers, FTP servers) accessible from the internet.
From CEH v13 Courseware:
* Module 03: Scanning Networks
* Topic: Network Address Translation
* Section: Types of NAT
CEH v13 Study Guide states:
"Static NAT provides a fixed translation of a private IP address to a public IP address. It is commonly used when an internal server must always be accessible from the Internet using a consistent IP address - this is known as server publishing." Incorrect Options:
* A. Overloading PAT: Multiple private IPs share a single public IP using port numbers - not suited for static mappings.
* B. Dynamic PAT: Similar to overloading; used for outbound traffic only.
* C. Dynamic NAT: Assigns a public IP from a pool; the mapping can change, not suitable for server publishing.
Reference:CEH v13 Study Guide - Module 3: Scanning Networks # NAT TypesRFC 3022 - Traditional NAT Terminology

Time-based blind SQL injection relies on observing delays introduced by database functions rather than visible error messages or returned data. When application responses vary only in timing, testers infer whether injected conditions evaluate as true. Error-based and UNION-based methods require information disclosure that is unavailable in this scenario.