In CEH v13 Module 16: Cloud Computing and Container Security, Kubernetes components are explained for understanding container orchestration risks.
Kube-scheduler is the master node component responsible for:
Assigning newly created pods to available nodes.
Evaluating each pod's resource requirements.
Considering node affinity/anti-affinity, data locality, hardware restrictions, etc.
Ensuring workload balancing across nodes.
Other Options:
A). Kube-controller-manager: Manages control loops for replication and status.
C). Kube-apiserver: Acts as the entry point for all REST commands.
D). Etcd: A key-value store used to save configuration data.
Reference:
Module 16 - Kubernetes Architecture and Security Risks
CEH eBook: Kubernetes Scheduler Role in Pod Lifecycle

Out-of-band SQL injection occurs when an attacker is unable to use an equivalent channel to launch the attack and gather results. ... Out-of-band SQLi techniques would believe the database server's ability to form DNS or HTTP requests to deliver data to an attacker. Out-of-band SQL injection is not very common, mostly because it depends on features being enabled on the database server being used by the web application. Out- of-band SQL injection occurs when an attacker is unable to use the same channel to launch the attack and gather results.
Out-of-band techniques, offer an attacker an alternative to inferential time-based techniques, especially if the server responses are not very stable (making an inferential time-based attack unreliable).
Out-of-band SQLi techniques would rely on the database server's ability to make DNS or HTTP requests to deliver data to an attacker. Such is the case with Microsoft SQL Server's xp_dirtree command, which can be used to make DNS requests to a server an attacker controls; as well as Oracle Database's UTL_HTTP package, which can be used to send HTTP requests from SQL and PL/SQL to a server an attacker controls.

According to CEH v13 Module 03: Scanning Networks, when using Nmap for service enumeration and fingerprinting, the flag to determine service version and type information is:
-sV - Version Detection Scan
nmap -sV <target IP> instructs Nmap to actively connect to open ports and probe the services running on those ports. This technique helps identify:
The service name (e.g., Apache, Nginx, etc.)
The version number (e.g., Apache 2.4.54)
The OS or device details (when possible)
This is especially useful when ports like 80 (HTTP) and 443 (HTTPS) are open, as it helps determine which web server is running (e.g., Apache, IIS, Nginx) and its version - which is critical for vulnerability assessment.
Why Other Options Are Incorrect:
A). -sv
# Incorrect syntax. Nmap flags are case-sensitive and this is a typo. Correct flag is -sV.
B). -Pn
Skips host discovery (ping scan). It does not provide service version info.
C). -V
Displays Nmap's version, not the service version on the target.
D). -ss
Incorrect spelling. You may have meant -sS (TCP SYN scan), which is for port scanning, not version detection.
Correct Option is A, assuming the intent is to write the correct syntax as -sV. However, strictly speaking, if this is a case-sensitive exam, and the listed option is -sv (lowercase 'v'), it would be invalid. But based on CEH exam context where minor casing issues are accepted if conceptually correct, A is the best answer.
Reference from CEH v13 Study Guide and Courseware:
Module 03 - Scanning Networks, Section: Nmap Scan Types and Options
EC-Council iLabs: Performing Version Detection Using nmap -sV
Nmap Official Docs (Referenced in CEH): https://nmap.org/book/man-version-detection.html
-h | findstr " -sV" -sV: Probe open ports to determine service/version info

Passwords are usually delineated as "hashed and salted". salting is simply the addition of a unique, random string of characters renowned solely to the site to every parole before it's hashed, typically this "salt" is placed in front of each password.
The salt value needs to be hold on by the site, which means typically sites use the same salt for each parole.
This makes it less effective than if individual salts are used.
The use of unique salts means that common passwords shared by multiple users - like "123456" or
"password" - aren't revealed revealed when one such hashed password is known - because despite the passwords being the same the immediately and hashed values are not.
Large salts also protect against certain methods of attack on hashes, including rainbow tables or logs of hashed passwords previously broken.
Both hashing and salting may be repeated more than once to increase the issue in breaking the security.

https://support.riverbed.com/content/support/software/steelcentral-npm/airpcap.html Since this question refers specifically to analyzing a wireless network, it is obvious that we need an option with AirPcap (Riverbed AirPcap USB-based adapters capture 802.11 wireless traffic for analysis). Since it works with two traffic analyzers SteelCentral Packet Analyzer (Cascade Pilot) or Wireshark, the correct option would be "Wireshark with Airpcap." NOTE: AirPcap adapters no longer available for sale effective January 1, 2018, but a question on this topic may occur on your exam.