In cybersecurity logging and source code version repositories, which compression approach is strictly mandatory and why?

Answer as guest — Start Free Practice Test to earn Practice PointsHow to earn pointsAsk a question+3Answer a question+1Someone answers yours+1Your Q gets upvoted+1Pioneer bonus (first 5)+5, ask questions & climb the leaderboard!

A Lossy, because it optimizes disk storage space much better than lossless formats.
B Lossless, because even a single altered or missing character can break code syntax or ruin forensic integrity.
C Lossy, because malicious code strings cannot execute when compressed in a lossy way.
D none

Show answer and explanation

Answer: B. Lossless, because even a single altered or missing character can break code syntax or ruin forensic integrity.

Answer: B) Lossless, because even a single altered or missing character can break code syntax or ruin forensic integrity.
Explanation: Text-based data, logs, database values, and executables cannot tolerate any data loss. Lossy compression discards subtle details, which in a text file or program script would result in corrupted parameters, inaccurate logs, or non-functional binaries.

Answering after opening this box earns no Practice Points.

Rules for asking and answering

In cybersecurity logging and source code version repositories, which compression approach is strictly mandatory and why?

More questions like this