CEHPC CertiProf Ethical Hacking Professional Certification Exam Free Practice Exam Questions (2026 Updated)

Identifying examples of social engineering is crucial for recognizing the diverse ways attackers attempt to circumvent technical security controls. A classic and highly effective example of social engineering is "vishing" (voice phishing), where an attacker calls a user and attempts to persuade them to disclose sensitive information, such as their network password, over the phone. This technique relies on the attacker's ability to sound professional, authoritative, or helpful, creating a scenario where the victim feels compelled to comply.

In contrast, options such as the use of antivirus software and periodic updating of the operating system are technical security controls. These are automated or administrative processes designed to protect the system's integrity from malware and exploits. Social engineering, however, bypasses these technical defenses by targeting the user directly. When an attacker asks for a password over the phone, they are not attempting to "break" the password through a brute-force attack; they are simply asking for the "key to the front door" by exploiting the user's trust.

This specific example highlights the concept of "Pretexting." The attacker may claim there is a critical security breach or a technical error on the user's account and that the password is required to "fix" the issue. Once the user discloses the password, the attacker has gained legitimate access to the system, often leaving no immediate trace of a technical intrusion. For an ethical hacker, documenting these types of vulnerabilities is essential. It demonstrates that even the most advanced firewall or antivirus cannot protect an organization if its employees are willing to give away credentials to an unverified caller. This reinforces the need for "Security Awareness Training," which teaches individuals that legitimate IT personnel will never ask for a full password over a phone call or through an unencrypted communication channel.

A private IP address is a fundamental element of network architecture used to enable communication between devices within a local network, such as a home, office, or enterprise environment. Unlike public IP addresses, which are globally unique and assigned by Internet Service Providers (ISPs) to identify a specific gateway to the internet, private IP addresses are reserved for internal use only. They are not routable on the public internet, which means a device with a private IP cannot be directly accessed by an outside computer without passing through a router or firewall.

The use of private IPs is governed by standards like RFC 1918, which defines specific ranges of addresses for private use, such as 192.168.x.x, 10.x.x.x, and 172.16.x.x through 172.31.x.x. This system allows thousands of devices on a local network to share a single public IP address through a process called Network Address Translation (NAT). This not only conserves the limited supply of IPv4 addresses but also provides a basic layer of security, as internal devices are effectively "hidden" from the public web.

For an ethical hacker, understanding the distinction between public and private IPs is crucial during the reconnaissance and scanning phases of a penetration test. During an internal pentest, the researcher will be working almost exclusively with private IPs to map out the organization's servers, workstations, and printers. In contrast, an external pentest focuses on the public IP of the organization's perimeter. Identifying a device's private IP can reveal its role in the network and help a tester understand the internal topology. Because private IPs are the "language" of local communication, securing the internal network involves ensuring that these private addresses are not being leaked or "spoofed" to gain unauthorized access to sensitive internal resources.

Persistent Cross-Site Scripting (XSS), also known as Stored XSS, is one of the most dangerous forms of web application vulnerabilities. It occurs when a web application receives data from a user and stores it permanently in its backend database or filesystem without proper sanitization or encoding. Common vectors for persistent XSS include comment sections, user profiles, message boards, and "Contact Us" forms. Unlike Reflected XSS, where the payload is included in a specific URL and only affects the user who clicks that link, a persistent XSS payload is served automatically to every user who visits the affected page.

When an attacker successfully injects a malicious script (typically JavaScript), the server "remembers" this script. Every time a legitimate user requests the page where the data is displayed, the server includes the malicious code in the HTML response. The user’s browser, trusting the source, executes the script. This can lead to devastating consequences, such as session hijacking through the theft of session cookies, account takeover, or the redirection of users to malicious websites. From an ethical hacking perspective, identifying persistent XSS involves testing all input fields that result in data being displayed later. Mitigation strategies focus on the principle of "filter input, escape output." Input should be validated against a strict whitelist of allowed characters, and any data rendered in the browser must be context-aware encoded (e.g., converting < to <) to prevent the browser from interpreting the data as executable code. Because the payload is stored on the server, this vulnerability represents a significant risk to the entire user base of an organization, making it a high-priority finding in any security assessment.

In the field of cybersecurity, it is a well-established axiom thatindividuals(the human element) represent the most vulnerable link in an organization's security chain. While a company can invest millions of dollars in sophisticated firewalls, encryption, and endpoint protection, these technical controls can be completely bypassed if a human is manipulated into granting access.

The vulnerability of individuals stems from several psychological factors:

Trust and Cooperation: Humans are naturally inclined to be helpful, which attackers exploit through social engineering.

Lack of Awareness: Employees who are not trained in security hygiene may use weak passwords, reuse credentials across multiple sites, or fail to recognize phishing attempts.

Fatigue and Urgency: Attackers often create a false sense of crisis (e.g., "Your account will be deleted in 1 hour") to trick users into bypassing their better judgment.

Physical Security Risks: Common vulnerabilities include "tailgating" (following someone through a secure door) or leaving sensitive documents on a desk.

Ethical hacking documents emphasize that a "Defense in Depth" strategy must include the "Human Firewall." This involves continuous security awareness training, phishing simulations, and clearAcceptable Use Policies (AUP). Organizations that ignore the human element often find themselves victims of ransomware or data breaches despite having state-of-the-art technical defenses. Strengthening the human link through education is the most effective way to reduce the overall attack surface of an organization.

Google Hacking, also known as Google Dorking, is a powerful reconnaissance strategy that involves using advanced search operators within the Google search engine to identify sensitive information or vulnerabilities that are inadvertently exposed on the public internet. By utilizing specific syntax—such as site:, filetype:, intitle:, and inurl:—an attacker or an ethical hacker can filter search results to find "low-hanging fruit" that would be impossible to locate with a standard query.

Common targets of Google Hacking include exposed database configuration files (which might contain passwords), server logs that reveal internal IP addresses, and "Index of" directories that provide a raw view of a server's file structure. For example, a search like filetype:env "DB_PASSWORD" could potentially reveal environment variables for web applications. This is an essential attack vector to mitigate because it requires no specialized hacking software; it simply exploits the fact that Google's crawlers have indexed files that administrators forgot to protect or hide via robots.txt.

Managing this vector involves "Self-Dorking"—regularly searching one's own domain using these advanced techniques to see what information is visible to the public. Mitigation strategies include proper server configuration, ensuring that sensitive files are not stored in the webroot, and using authentication for all administrative interfaces. From a penetration testing perspective, Google Hacking is part of the "Passive Reconnaissance" phase, allowing a tester to gather intelligence about a target's infrastructure without ever sending a single packet directly to the target's servers. This highlights how easily information leakage can lead to a full system compromise if not actively monitored.

Google Dorking, also known as Google Hacking, is a passive reconnaissance technique that involves using advanced search operators to filter through the vast index of the Google search engine. It is important to clarify that Google Dorks do not "hack" computers or websites themselves; rather, they utilize the search engine's indexing power to find information that has already been made public—often inadvertently. By using specific strings like filetype:log, intitle:"index of", or inurl:admin, a researcher can locate sensitive directories, exposed log files, or configuration pages that were never intended to be indexed by search bots.

From a threat management perspective, Google Dorking is a double-edged sword. Ethical hackers use it during the information-gathering phase of a penetration test to see what an organization is leaking to the public web. This might include SQL error messages, which can reveal database structures, or publicly accessible backup files containing sensitive credentials. However, the tool itself is not a "backdoor" or an exploit; it is a sophisticated way of querying a database of cached website content.

If a computer or server appears in a Google Dork result, it typically means the administrator failed to configure the robots.txt file or server permissions correctly, allowing Google’s crawlers to document the internal structure. Managing this threat involves regular "dorking" of one's own domain to ensure that no sensitive paths or files are visible to the public. Understanding that Google Dorks are simply advanced search queries helps security professionals realize that the "leak" occurs at the server configuration level, not within the search engine itself. Consequently, remediation focuses on tightening access controls and ensuring that internal-only resources are not reachable or indexable by external search engines.

Google Dorks, also known as Google hacking, areadvanced search queriesthat use specific operators to locate publicly accessible information indexed by search engines. Therefore, option A is the correct answer.

Google Dorks donot hack systems, compromise computers, or act as backdoors. Instead, they reveal information that is already publicly available but may be unintentionally exposed due to poor configuration. Examples include exposed login pages, backup files, configuration files, error messages, or sensitive documents that should not be indexed.

Option B is incorrect because Google Dorks do not provide unauthorized access to web pages. Option C is also incorrect because Google Dorks do not exploit vulnerabilities or bypass authentication mechanisms.

From an ethical hacking perspective, Google Dorks are commonly used during thepassive reconnaissance phaseto identify information leakage without directly interacting with the target system. This makes them low-impact but highly effective for discovering misconfigurations.

Understanding Google Dorks is important for managing information exposure risks. Ethical hackers use them to demonstrate how attackers can gather intelligence without triggering security alerts. Defenders can mitigate these risks by properly configuring robots.txt files, access controls, and removing sensitive content from public indexing.

Nessus is a globally recognized, industry-standardvulnerability scannerused by security professionals to identify security flaws in a network, operating system, or application. Developed by Tenable, it is a comprehensive tool that automates the process of finding weaknesses such as unpatched software, weak passwords, misconfigurations, and "zero-day" vulnerabilities.

Nessus operates by probing a target system and comparing the results against an extensive, constantly updated database of thousands of known vulnerabilities (plugins). The scanning process typically involves:

Host Discovery: Identifying which devices are active on the network.

Port Scanning: Checking for open services and identifying their versions.

Vulnerability Assessment: Running specific checks to see if those services are susceptible to known exploits.

Compliance Auditing: Ensuring that systems meet specific security standards like PCI DSS or HIPAA.

Unlike "automated hacking" tools that focus on exploitation, Nessus is adiagnostic tool. It provides detailed reports that categorize vulnerabilities by severity (Critical, High, Medium, Low) and offers specific remediation advice on how to fix the issues. In a professional penetration test, Nessus is used during the "Vulnerability Analysis" phase to provide a broad map of the target's weaknesses. This allows the tester to prioritize which flaws to attempt to exploit manually. Regular use of Nessus is a cornerstone of any proactive vulnerability management program.

Malware, short for "malicious software," is a broad category of software specifically engineered to perform unauthorized and often harmful actions on a computer system, network, or device. Its primary characteristic is that it operateswithout the owner's consent. Malware is the primary tool used by cybercriminals to achieve various objectives, ranging from financial gain to corporate espionage and simple disruption.

Malware encompasses several distinct types, each with its own method of infection and goal:

Viruses and Worms: Designed to spread from one file or computer to another, often damaging data or consuming network bandwidth along the way.

Trojan Horses: Programs that disguise themselves as legitimate software to trick users into installing them, only to reveal a malicious "payload" once active.

Ransomware: Encrypts the victim's data and demands payment for the decryption key.

Spyware and Stealers: Secretly monitor user activity or steal sensitive information like passwords and credit card numbers.

Rootkits: Specialized malware designed to provide high-level "root" access while remaining hidden from the operating system and antivirus software.

Ethical hackers study malware to understand how to defend against it. This involves analyzing "Attack Vectors" (how malware enters a system), "Persistence Mechanisms" (how it stays there), and "Command and Control" (how it communicates with the attacker). Protecting against malware requires a multi-layered defense strategy, including updated antivirus software, strictAcceptable Use Policies (AUP), and regular vulnerability scanning to close the gaps that malware exploits to infect systems.

Secure Shell (SSH) is a robust cryptographic network protocol utilized for operating network services securely over an unsecured network. Its primary application is the secure remote login to computer systems by administrators and users. Unlike earlier protocols such as Telnet or rlogin, which transmitted data (including passwords) in plain text, SSH provides a secure, encrypted channel. It achieves this through a suite of cryptographic techniques that ensure theconfidentiality,integrity, andauthenticityof the data being transmitted between the client and the server.

The protocol operates using a client-server architecture, where an SSH client initiates a connection to an SSH server. SSH facilitates both authentication and authorization. Authentication is typically performed using either a password or, more securely, a public-private key pair. Once the user's identity is verified, the protocol authorizes the level of access based on the server's configuration. Beyond simple terminal access, SSH supports secure file transfers (SFTP) and port forwarding, allowing other network protocols to be "tunneled" through its encrypted connection. From a security standpoint, while SSH is highly secure, it can be breached if misconfigured—such as by allowing weak passwords or failing to disable root login. Consequently, ethical hackers prioritize hardening SSH services as a fundamental control in protecting organizational assets.

Nmap is the primary tool used forport scanning, making option B the correct answer. Port scanning is a core activity during the reconnaissance and scanning phases of penetration testing, where the goal is to identify open, closed, or filtered ports on target systems.

Nmap allows ethical hackers to discover which services are running, their versions, and potential misconfigurations. It supports multiple scan types, including TCP SYN scans, UDP scans, and service detection scans, making it highly versatile and efficient.

Option A is incorrect because Metasploit is primarily an exploitation framework, not a dedicated port scanner. Option C is incorrect because Shodan is an internet-wide search engine, not a direct scanning tool used against specific targets.

Understanding port scanning is essential for identifying attack surfaces. Open ports often expose services that may contain vulnerabilities or misconfigurations. Ethical hackers use Nmap responsibly to map networks and guide further testing.

From a defensive perspective, regular port scanning helps organizations identify unnecessary services and enforce least-exposure principles. Nmap remains one of the most fundamental tools in ethical hacking and network security.