After 30 minutes your scan stops with an out-of-session error. What could be the cause of error?
-
Redundant path limit was too low
-
A parameter was not tracked
-
Flash parsing was turned off
-
Platform authentication was not configured
AppScan out-of-session errors occur when the scanner loses its session context. After 30 minutes, sessions commonly expire. If a session parameter (cookie, URL token) isn't tracked (B), AppScan can't maintain session state and loses access. Redundant path (A), Flash parsing (C), and platform authentication (D) don't directly cause session loss.
To answer this question, 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 cause an out-of-session error during a scan. The redundant path limit refers to the number of alternative paths that a packet can take through a network, and it is not directly related to a scan session error.
Option B) A parameter was not tracked - This option is correct. In a scan session, it is important to track and monitor all parameters to ensure the session runs smoothly. If a parameter is not tracked, it can lead to errors and disruptions in the scan, causing the session to stop with an out-of-session error.
Option C) Flash parsing was turned off - This option is incorrect. Flash parsing refers to the process of parsing flash memory data in a system, and it is not directly related to a scan session error. Turning off flash parsing would not cause an out-of-session error during a scan.
Option D) Platform authentication was not configured - This option is incorrect. Platform authentication refers to the process of authenticating a user or device on a platform, and it is not directly related to a scan session error. Not configuring platform authentication would not cause an out-of-session error during a scan.
Therefore, the correct answer is Option B) A parameter was not tracked. This option is correct because if a parameter is not tracked during a scan session, it can lead to errors and disruptions, causing the session to stop with an out-of-session error.