- A
The server blocks the PUT method for that specific URI.
405 precisely means the method is not allowed for the requested resource.
- B
The PUT method is allowed but the resource does not exist.
Why wrong: If the resource does not exist, the server would return 404 Not Found.
- C
The server does not support the PUT method.
Why wrong: The server may support PUT on other resources; 405 is resource-specific.
- D
The request was malformed and rejected.
Why wrong: A malformed request typically results in a 400 Bad Request.
Quick Answer
The correct interpretation is that the server blocks the PUT method for that specific URI. This occurs because the web server recognizes PUT as a valid HTTP method but has an explicit access control rule—such as an Apache `<LimitExcept>` directive or IIS request filtering—that denies it for that endpoint, meaning the request reached the server and was processed but was refused at the configuration level. On the CompTIA PenTest+ PT0-002 exam, this tests your ability to distinguish between a server rejecting a method entirely (which would yield a 501 Not Implemented) versus actively forbidding it for a particular resource, a common trap where testers mistakenly assume the method is unsupported. Remember the mnemonic: “405 = Forbidden Function, not Forgotten Function”—the server knows the verb but says “no” to that path.
PT0-002 Practice Question: Information Gathering and Vulnerability Scanning
This PT0-002 practice question tests your understanding of information gathering and vulnerability scanning. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
During a vulnerability scan of a web application, a tester receives an HTTP response with a '405 Method Not Allowed' error when trying to use a PUT request. What does this indicate about the web server's configuration?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The server blocks the PUT method for that specific URI.
A 405 Method Not Allowed error indicates that the server recognized the PUT method as valid but has explicitly disallowed it for the requested URI. This is a server-level access control configuration, often enforced via web server directives (e.g., Apache's `<LimitExcept>` or IIS's request filtering) or application-level routing rules. The tester's PUT request reached the server and was processed, but the server's configuration prevented it from being fulfilled for that specific endpoint.
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.
- ✓
The server blocks the PUT method for that specific URI.
Why this is correct
405 precisely means the method is not allowed for the requested resource.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The PUT method is allowed but the resource does not exist.
Why it's wrong here
If the resource does not exist, the server would return 404 Not Found.
- ✗
The server does not support the PUT method.
Why it's wrong here
The server may support PUT on other resources; 405 is resource-specific.
- ✗
The request was malformed and rejected.
Why it's wrong here
A malformed request typically results in a 400 Bad Request.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse a 405 Method Not Allowed with a 501 Not Implemented, mistakenly thinking the server lacks PUT support entirely, when in fact the server supports PUT but has been configured to deny it for that specific URI.
Detailed technical explanation
How to think about this question
The 405 status code is defined in RFC 7231, Section 6.5.5, and requires the server to include an Allow header in the response listing the permitted methods for that URI. In practice, web servers like Apache use `<LimitExcept>` or `.htaccess` files to block specific HTTP methods on a per-directory or per-file basis, while application frameworks (e.g., Django, Flask) may enforce method restrictions at the route level. A tester can confirm this by checking the Allow header and testing other methods like OPTIONS to enumerate allowed verbs.
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.
TExam Day Tips
- 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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Information Gathering and Vulnerability Scanning — study guide chapter
Learn the concepts, then practise the questions
- →
Information Gathering and Vulnerability Scanning practice questions
Targeted practice on this topic area only
- →
All PT0-002 questions
509 questions across all exam domains
- →
CompTIA PenTest+ PT0-002 study guide
Full concept coverage aligned to exam objectives
- →
PT0-002 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PT0-002 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Planning and Scoping practice questions
Practise PT0-002 questions linked to Planning and Scoping.
Information Gathering and Vulnerability Scanning practice questions
Practise PT0-002 questions linked to Information Gathering and Vulnerability Scanning.
Attacks and Exploits practice questions
Practise PT0-002 questions linked to Attacks and Exploits.
Reporting and Communication practice questions
Practise PT0-002 questions linked to Reporting and Communication.
Tools and Code Analysis practice questions
Practise PT0-002 questions linked to Tools and Code Analysis.
PT0-002 fundamentals practice questions
Practise PT0-002 questions linked to PT0-002 fundamentals.
PT0-002 scenario practice questions
Practise PT0-002 questions linked to PT0-002 scenario.
PT0-002 troubleshooting practice questions
Practise PT0-002 questions linked to PT0-002 troubleshooting.
Practice this exam
Start a free PT0-002 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PT0-002 question test?
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: The server blocks the PUT method for that specific URI. — A 405 Method Not Allowed error indicates that the server recognized the PUT method as valid but has explicitly disallowed it for the requested URI. This is a server-level access control configuration, often enforced via web server directives (e.g., Apache's `<LimitExcept>` or IIS's request filtering) or application-level routing rules. The tester's PUT request reached the server and was processed, but the server's configuration prevented it from being fulfilled for that specific endpoint.
What should I do if I get this PT0-002 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
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.