Most Efficient Sensitive-File Exfiltration Method

PT0-003 By islever Editorial Last updated

Summarize concepts related to staging and exfiltration. Given a scenario, perform network attacks using the appropriate tools.

Short answer

D Encrypt the sensitive file and transmit it over HTTPS for fast, protected exfiltration.

Question

Which of the following is the most efficient way to exfiltrate a file containing data that could be sensitive?
  1. Use steganography and send the file over FTP.
  2. Compress the file and send it using TFTP.
  3. Split the file in tiny pieces and send it over dnscat.
  4. Encrypt and send the file over HTTPS. Correct Answer

Key Takeaways

It tests objective 5.3 — choosing an exfiltration channel by throughput and detectability, with the trap that stealthier channels like dnscat DNS tunneling are far slower, not more efficient.

This PT0-003 scenario tests exfiltration channel efficiency, and the answer is D: encrypting the file and sending it over HTTPS gives high-throughput, reliable, low-noise transfer.

Common mistake: Option C, splitting the file into tiny pieces over dnscat, is the tempting pick because DNS tunneling evades firewalls, but DNS payloads are minuscule and need reassembly, making it the least efficient choice.

Expert Analysis

The Governing Principle

The CompTIA PT0-003 exfiltration doctrine (objective 5.3, staging and exfiltration) judges a channel on throughput, reliability and how much it stands out on the wire. The word "efficient" in the stem is the deciding constraint: the winning method must move the whole file quickly, intact and without requiring unusual encoding work.

Applying It to the Options

  • Option D — encrypt and send over HTTPS is correct. TLS over TCP port 443 delivers full-bandwidth, connection-oriented, guaranteed-delivery transfer that blends into normal browsing traffic, so no extra concealment or reassembly is needed. Encryption also satisfies the "could be sensitive" requirement by protecting the file in transit.
  • Option C — split into tiny pieces over dnscat is the classic trap. DNS tunneling is stealthy and often slips past egress filters, but DNS packets carry only tiny payloads, so throughput is extremely low and the transfer requires custom splitting and reassembly — precise and reliable, but the opposite of efficient.
  • Option A — steganography over FTP adds encoding overhead and uses cleartext FTP, which is easily sniffed and flagged; hiding the payload costs bandwidth and time.
  • Option B — compress and send via TFTP uses UDP with no delivery guarantee and a trivially detectable unauthenticated protocol, so the file may need retransmission.

Why the Comments Converge

Community reasoning echoes this: one note stresses that HTTPS protects data in transit with TLS and, unlike DNS tunneling or steganography, needs no unusual encoding, fragmentation or concealment; another flags that "efficient" is the operative adjective. Both land on D, and the official logic of the exfiltration domain agrees.

Exam Strategy

On efficiency-worded exfiltration questions, rank each channel by throughput and delivery guarantee before considering stealth: connection-oriented protocols over common ports beat tunneling and covert channels. Treat fragmentation, encoding and reassembly steps as efficiency penalties, and reserve low-and-slow DNS or steganographic methods for questions that explicitly ask for stealth or evasion.

Frequently Asked Questions

Why is HTTPS exfiltration more efficient than DNS tunneling with dnscat?

HTTPS carries large payloads over a full TCP connection with guaranteed delivery, while dnscat sends tiny DNS queries and responses, forcing the file into fragments that must be reassembled slowly.

Does encrypting the file before sending it over HTTPS matter?

Yes. TLS already protects data in transit, but encrypting the file itself adds at-rest protection if a copy is later captured, and it costs negligible time compared with the transfer.

When would steganography or TFTP be a better choice than HTTPS?

They would not be more efficient. Steganography trades bandwidth for concealment when stealth is the priority, and TFTP suits trusted local LAN transfers of unattended files, not sensitive data over the internet.

More PT0-003 FAQ →

Community Votes

D
74%
C
15%
A
12%

74% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 2 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 2

  1. leesuh 👍 2 Answered D
    A. Steganography over FTP ❌ • Steganography hides data inside images or media. • FTP is unencrypted → can be detected/sniffed. • Less efficient and more detectable. B. Compress file and use TFTP ❌ • TFTP is unencrypted and connectionless, very easy to detect, and doesn’t guarantee delivery. C. Split file and send over dnscat ❌ • dnscat uses DNS tunneling, can bypass some firewalls. • Splitting files into tiny pieces is slow and inefficient, especially for large files. D. Encrypt and send over HTTPS ✅ • HTTPS is encrypted, reliable, and allowed through most firewalls. • Encrypting the file adds an extra layer of security. • Efficient: sends the file in one piece over a standard protocol.
  2. sneeed 👍 1 Answered D
    Pay attention to the adjective, 'efficient'. Correct answer: D. Encrypt and send the file over HTTPS. HTTPS uses TLS to protect data during transmission. Unlike DNS tunneling or steganography, it doesn't require unusual encoding, fragmentation, or concealment techniques.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All PT0-003 Questions

Access 120 questions with complete answers and detailed explanations.

View Full PT0-003 Practice Test →

← Back to PT0-003 Study Guide