If track data inconsistency is detected during mission execution, what action should be taken before engagement?

If track data inconsistency is detected during mission execution, what action should be taken before engagement?

• A. Ignore and continue tracking.
• B. Rely solely on a single sensor.
• C. Flag the track for human review and revalidate before engagement.
• D. Engage immediately to test sensors.

Answer: (C)

Data integrity and safe decision-making demand verification when sensor information looks inconsistent. If the track data doesn’t align across sensors or seems unreliable, you should pause engagement and bring it to human review, then revalidate before acting. This human-in-the-loop check helps confirm the target’s identity and the track’s accuracy, reducing the risk of misidentification or unnecessary escalation due to faulty data. Ignoring the inconsistency, relying on a single sensor, or engaging immediately to test sensors all bypass essential validation steps and raise the chance of false or dangerous actions. Flagging for review and revalidation is the cautious, correct approach that preserves accuracy and safety before any engagement.

Data integrity and safe decision-making demand verification when sensor information looks inconsistent. If the track data doesn’t align across sensors or seems unreliable, you should pause engagement and bring it to human review, then revalidate before acting. This human-in-the-loop check helps confirm the target’s identity and the track’s accuracy, reducing the risk of misidentification or unnecessary escalation due to faulty data.

Ignoring the inconsistency, relying on a single sensor, or engaging immediately to test sensors all bypass essential validation steps and raise the chance of false or dangerous actions. Flagging for review and revalidation is the cautious, correct approach that preserves accuracy and safety before any engagement.