hardMultiple Choice
PT0-002 Practice Question: The scope allows only Nmap, but it is ineffective…
The scope allows only Nmap, but it is ineffective against heavy packet filtering. The tester wants to use an alternate tool. What should the tester do?
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
✓
Request approval from the client to use a different tool
Request approval from the client to use a different tool. Since the scope explicitly limits testing to Nmap, using any other tool would violate the agreed rules of engagement, so the tester must obtain written client authorization before substituting a different tool. Options B and D are wrong because they either bypass the scope restriction or continue with the ineffective Nmap approach without addressing the filtering problem. Option C is also incorrect because the engagement is not necessarily untestable—an approved alternate tool could still accomplish the objectives.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Request approval from the client to use a different tool
Why this is correct
The scope explicitly permits only Nmap, so introducing another tool breaches the agreed rules of engagement. Requesting client approval first keeps the tester within authorisation; using an unapproved tool, however effective against packet filtering, would be unauthorised testing.
- ✗
Use the alternate tool and note it in the report
Why it's wrong here
The scope authorises only Nmap, so running an unapproved tool breaches the rules of engagement regardless of reporting it afterwards. Documentation does not grant permission. Requesting a scope amendment is the compliant path. The temptation is pragmatism: the tool would work, and disclosure feels transparent, but consent must precede action.
- ✗
Abort the scan and report that the network is not testable
Why it's wrong here
Aborting overstates the obstacle: Nmap remains usable, and packet filtering can be worked around within scope via timing templates, fragmentation or alternate scan types. Declaring the network untestable also abandons the engagement without seeking a scope amendment. Aborting suits genuine blockers such as a total outage or withdrawn authorisation.
- ✗
Use Nmap with different parameters
Why it's wrong here
Varying Nmap parameters stays within the authorised tool but cannot overcome heavy packet filtering, so the engagement stalls. The tempting path is that tuning timing and probes feels like progress; however, the scope explicitly permits only Nmap, so the tester must request a scope change before using an alternate tool.
Go deeper
Related to this question
Learn chapter
PowerShell for Penetration Testing
Key term
Authorization
Authorization determines what an authenticated user is allowed to do within a system, such as accessing files, running programs, or changing settings.
Key term
Scope
In IT, scope defines the boundaries, goals, and deliverables of a project, assessment, or engagement, specifying what is included and what is excluded.
About these practice questions
Courseiva writes every PT0-003 question from scratch — 777 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PT0-003 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-003 exam.