To answer this question, you need to understand the possible causes of an "out-of-session" error during a scan. Let's go through each option to understand why it is correct or incorrect:
Option A) Redundant path limit was too low - This option is incorrect because a low redundant path limit would not directly cause an "out-of-session" error. The redundant path limit refers to the number of alternate paths that a packet can take in a network, and it is not directly related to a scan session error.
Option B) A parameter was not tracked - This option is correct because a parameter not being tracked can lead to an "out-of-session" error during a scan. When scanning a website or application, it is essential to track and include all relevant parameters to ensure the scan remains in session. If a parameter is missed or not properly tracked, the scan may encounter an "out-of-session" error.
Option C) Flash parsing was turned off - This option is incorrect because turning off flash parsing would not directly result in an "out-of-session" error. Flash parsing refers to the process of analyzing Flash content on a website, and it is not directly related to a scan session error.
Option D) Platform authentication was not configured - This option is incorrect because the absence of platform authentication would not directly cause an "out-of-session" error. Platform authentication refers to the process of authenticating and verifying the identity of users or devices accessing a platform, and it is not directly related to a scan session error.
The correct answer is B) A parameter was not tracked. This option is correct because if a parameter is not tracked during a scan, it can lead to an "out-of-session" error.