Why record plugin configuration before testing?

• A. To bypass policy restrictions
• B. To ensure results can be repeated
• C. To speed up the test
• D. To randomize the scan results

Answer: (B)

Recording plugin configuration before testing centers on making results repeatable. The set of plugin checks, their order, thresholds, and timing all shape what the scan discovers. By saving the exact configuration (and plugin versions), you can re-run the same test later and expect the same outcomes, which is essential for validating findings, building credible reports, and allowing others to reproduce your work. If results change on a subsequent run, you have a concrete basis to compare against—likely the configuration differs, not the target. This approach emphasizes deterministic, trustworthy testing, rather than speeding things up or introducing randomness.