The correct answer is hardcoded credentials because the error log explicitly reveals a database connection warning where a username and password, such as 'test' with its corresponding password, are embedded directly in the source code rather than being stored securely. This log entry indicates that the application is exposing authentication secrets in plaintext, which is a classic sign of hardcoded credentials—a vulnerability that allows attackers to extract sensitive access information from error messages or decompiled code. On the CompTIA PenTest+ PT0-002 exam, this scenario tests your ability to distinguish between common web vulnerabilities by reading server logs; a common trap is confusing a credential leak with SQL injection, but the key clue is the absence of query syntax or database error output. Remember the mnemonic “Log Leaks Login” to recall that any error log displaying a user and password string points directly to hardcoded credentials, not code injection.
PT0-002 Practice Question: Information Gathering and Vulnerability Scanning
This PT0-002 practice question tests your understanding of information gathering and vulnerability scanning. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
[Sun Mar 13 12:00:00.123456 2024] [php:notice] [pid 1234] [client 192.168.1.5:54321] PHP Notice: Undefined variable: username in /var/www/html/login.php on line 32
[Sun Mar 13 12:00:01.234567 2024] [php:warning] [pid 1234] [client 192.168.1.5:54321] PHP Warning: mysqli_connect(): (HY000/1045): Access denied for user 'test'@'localhost' (using password: YES) in /var/www/html/db.php on line 8
Refer to the exhibit. A penetration tester is reviewing a web server error log. Based on the log, what vulnerability does the tester suspect?
Refer to the exhibit.
[Sun Mar 13 12:00:00.123456 2024] [php:notice] [pid 1234] [client 192.168.1.5:54321] PHP Notice: Undefined variable: username in /var/www/html/login.php on line 32
[Sun Mar 13 12:00:01.234567 2024] [php:warning] [pid 1234] [client 192.168.1.5:54321] PHP Warning: mysqli_connect(): (HY000/1045): Access denied for user 'test'@'localhost' (using password: YES) in /var/www/html/db.php on line 8
A
Cross-site scripting
Why wrong: No user input is reflected in the output.
B
SQL injection
Why wrong: No SQL queries are visible in the log.
C
Remote code execution
Why wrong: No code execution is indicated.
D
Hardcoded credentials
The log reveals a database connection attempt with a username and password, suggesting credentials are hardcoded in the source code.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Hardcoded credentials
Option D is correct because the warning shows that a password is being used for database connection, and the message indicates hardcoded credentials (user 'test' with a password) are present in the code. Option A (XSS) is not evident. Option B (SQL injection) is not shown. Option C (remote code execution) is not indicated.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Cross-site scripting
Why it's wrong here
No user input is reflected in the output.
✗
SQL injection
Why it's wrong here
No SQL queries are visible in the log.
✗
Remote code execution
Why it's wrong here
No code execution is indicated.
✓
Hardcoded credentials
Why this is correct
The log reveals a database connection attempt with a username and password, suggesting credentials are hardcoded in the source code.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Trap categories for this question
Command / output trap
No user input is reflected in the output.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this PT0-002 question in full detail.
Identify which PT0-002 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Information Gathering and Vulnerability Scanning — This question tests Information Gathering and Vulnerability Scanning — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Hardcoded credentials — Option D is correct because the warning shows that a password is being used for database connection, and the message indicates hardcoded credentials (user 'test' with a password) are present in the code. Option A (XSS) is not evident. Option B (SQL injection) is not shown. Option C (remote code execution) is not indicated.
What should I do if I get this PT0-002 question wrong?
Identify which PT0-002 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PT0-002 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PT0-002 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.