PenTest+ Post-exploitation and Lateral Movement: 122 practice questions
12 of the 122 Post-exploitation and Lateral Movement questions in the Certsqill PenTest+ bank, shown in full below. Each one carries an explanation for every option, not just the correct one — the wrong answers are where the marks go.
Preparing for PenTest+? Take the free 5-min readiness check →
1. The route supports pivoting to another reachable resource: What is the strongest supported conclusion?
- Data exfiltration was confirmed.Reachability does not show that data was collected or transferred to any destination.
- The route supports pivoting to another reachable resource. ✓Pivoting uses an accessible host or route to reach another resource without requiring privilege escalation.
- Privilege escalation occurred.The account retained the same restricted rights, so increased privilege was not demonstrated.
- Persistence was established across restart or credential changes.No mechanism showing survival across restart or credential events was observed.
The evidence supports pivoting or lateral reachability, not escalation, persistence, or confirmed exfiltration.
2. Remove LabValidation and preserve logs: What should the assessor do next?
- Disable the entire Task Scheduler service.Disabling the service could disrupt legitimate workloads and is broader than removing the test task.
- Delete all scheduled tasks.Broad deletion could remove legitimate client tasks and exceeds the required cleanup.
- Remove LabValidation and preserve logs. ✓The assessor should remove the testing artifact while preserving audit evidence.
- Delete audit logs recording the task creation event.Audit logs are evidence and must remain intact under the stated requirement.
Remove only the assessor-created task and preserve the audit logs.
3. Scheduled task: Which root cause best explains the artifact?
- Scheduled task ✓The identified Task Scheduler entry directly explains execution triggered at system startup.
- Startup-folder entry with a user logon triggerA startup-folder entry explains execution at user logon, not the explicitly identified Task Scheduler entry at system startup.
- Startup serviceA service can provide startup execution, but the evidence specifically identifies a Task Scheduler entry rather than a service.
- Registry autorunA registry autorun can trigger startup execution, but it does not explain the identified scheduled-task artifact.
The identified Task Scheduler entry explains the startup-triggered execution.
4. Use tar, then gzip, then adb pull: Which command sequence best matches the requirement?
- Use adb pull.adb pull transfers files but does not archive or compress the multiple source files.
- Use gzip, then adb pull.gzip compresses data but does not combine multiple files into the required archive.
- Use tar, then gzip, then adb pull. ✓tar combines the approved files, gzip compresses the archive locally on the device, and adb pull transfers only that resulting archive.
- Use tar, then adb pull.tar creates one archive and adb pull transfers it, but the sequence omits the required compression.
Create the archive with tar, compress it with gzip, then transfer it with adb pull.
5. A valid authorized account: What prerequisite is missing?
Exhibit:route: jump-stg -> 10.40.5.20 TCP/5985: reachable WinRM response: access denied credential set: noneWhat prerequisite is missing?
- A valid authorized account ✓Routing reaches the service, but authentication and permissions still require valid authorized credentials.
- A different destination addressThe supplied destination responds on the expected port, so changing addresses does not address access denial.
- A second proxy protocolA second proxy is unnecessary when the target service is already reachable through the confirmed route.
- Another network routeThe exhibit confirms a working route and reachable service, so an additional path is not the missing prerequisite.
The route works; valid authorized credentials are required before the reachable WinRM service can authenticate.
6. Restore the agreed firewall baseline: What control should be recommended?
- Hash the temporary rule.Hashing can support integrity comparison but does not restore the firewall’s intended access control.
- Restore the agreed firewall baseline. ✓Removing the temporary rule and verifying the agreed baseline addresses the residual exposure without deleting audit evidence.
- Create a second inbound rule.Adding another rule could broaden exposure and does not restore the agreed configuration.
- Delete the firewall audit logs.Audit logs should be preserved; deleting them removes evidence without correcting the exposed rule.
Restore and verify the agreed firewall baseline, while preserving audit records and documenting residual artifacts.
7. The service may provide persistence: What conclusion is best supported?
- Reverse connection occurred.No outbound command-and-control traffic was observed, so a reverse connection is unsupported.
- The service is a confirmed malicious implant.Automatic startup and a writable path warrant investigation but do not prove malicious intent by themselves.
- Lateral movement occurred.The evidence does not show access to another host or resource, which is required to conclude lateral movement.
- The service may provide persistence. ✓Automatic service startup can maintain execution across restarts, while the evidence does not establish maliciousness.
Automatic service startup supports possible persistence, but does not prove malicious intent or movement.
8. Compress, then encrypt: Which operation sequence is appropriate?
- Encrypt only.Encryption protects content but does not satisfy the explicit requirement to reduce transfer size.
- Embed the archive in an image.Steganography conceals data within cover media but does not inherently compress or encrypt its contents.
- Compress only.Compression reduces size but leaves the archive’s contents unprotected from disclosure.
- Compress, then encrypt. ✓Compression reduces size, and encryption subsequently protects the archive’s contents during approved handling.
Compression addresses size, and encryption separately addresses confidentiality for the approved synthetic archive.
9. WinRM reachable: What conclusion is strongest?
Exhibit:TCP/5985: open WinRM service response: HTTP 401 Unauthorized TCP/135: no response WMI execution result: not obtainedWhat conclusion is strongest?
- No remote service exists.The open port and WinRM response directly contradict the conclusion that remote management is absent.
- WMI remote execution succeeded.TCP/135 provided no response and no WMI result was obtained, so successful WMI execution is unsupported.
- WinRM reachable; auth unproven. ✓The open WinRM port and 401 response support reachability while showing that authentication was not established.
- A lateral path is proven.Reachability and an authentication challenge do not prove successful authentication, execution, or access to another resource.
The evidence supports WinRM reachability and an authentication challenge, not successful execution or lateral movement.
10. Test revoked sign-in: What should the team do next?
- Test revoked sign-in; review its audit event. ✓A bounded synthetic sign-in attempt and its audit event directly verify that revocation took effect.
- Test the revoked credential against a production identity provider for confirmation.Production testing exceeds the synthetic-tenant boundary and is unnecessary for this validation.
- Delete the tenant audit logs after the credential test to remove temporary evidence.Deleting logs destroys evidence and does not validate the credential's authentication status.
- Rotate an unrelated tenant key and review its resulting audit record.An unrelated key does not test whether the revoked credential can still authenticate.
Attempt a permitted synthetic sign-in and review its audit event.
11. A registry autorun entry triggering at login: Which root cause is most supported?
- A service-based pivot to another host.The observation shows local login execution, not service execution or access to another host.
- A scheduled task mechanism.No scheduled task was observed; the supplied artifact is a registry Run-key value.
- A reverse shell maintaining an outbound session.No outbound connection was observed, so the evidence does not support a reverse shell.
- A registry autorun entry triggering at login. ✓A Run-key value that launches code at login is a registry autorun mechanism and may provide persistence.
The login-triggered Run-key value identifies a registry autorun artifact and possible persistence mechanism.
12. Embed it with steghide: Which tool or method best fits?
- Encrypt the canary with OpenSSL before placing it in the image.Encryption protects contents but does not inherently conceal that data exists in the image.
- Use Base64 encoding.Base64 represents data as text and does not conceal it within an image.
- Embed it with steghide. ✓Steghide embeds data within cover media, matching the concealment requirement.
- Use gzip compression to reduce its size.Compression changes representation and size but does not hide data within cover media.
Steghide provides steganographic concealment within image cover media.
110 more Post-exploitation and Lateral Movement questions
The remaining 110 questions in this domain are part of the full PenTest+ bank — 870 questions, every option explained. Start with the free five-minute check and see your score per domain.
Test your PenTest+ readiness — freeOther PenTest+ domains
- Attacks and Exploits — 304 questions →
- Reconnaissance and Enumeration — 183 questions →
- Vulnerability Discovery and Analysis — 148 questions →
- Engagement Management — 113 questions →
- All 870 PenTest+ questions →
- PenTest+ certification: requirements, cost and exam format →