If a bad resolve is identified, what action should be taken to prevent downstream issues?

If a bad resolve is identified, what action should be taken to prevent downstream issues?

• A. Delete it.
• B. Keep it.
• C. Rename it.
• D. Archive it.

Answer: (A)

When a bad resolve is identified, delete it from the active dataset. Removing the faulty entry prevents any downstream process from using it, which stops misrouting, incorrect lookups, or policy mistakes that could cascade through the system. Keeping it around allows the error to propagate; renaming it doesn’t fix the underlying issue and can mislead users and systems, while archiving may preserve a record but can still be surfaced or reactivated later, risking the same problems. Deleting preserves data integrity and ensures downstream workflows aren’t affected, with an opportunity to log the incident for auditing and remediation.

When a bad resolve is identified, delete it from the active dataset. Removing the faulty entry prevents any downstream process from using it, which stops misrouting, incorrect lookups, or policy mistakes that could cascade through the system. Keeping it around allows the error to propagate; renaming it doesn’t fix the underlying issue and can mislead users and systems, while archiving may preserve a record but can still be surfaced or reactivated later, risking the same problems. Deleting preserves data integrity and ensures downstream workflows aren’t affected, with an opportunity to log the incident for auditing and remediation.