What types of troubleshooting can you do when uploading firmware? (Choose two.)

If a firmware upload fails or causes unexpected issues, investigating whether the firmware image file is corrupted (e.g., checksum mismatch) is a crucial troubleshooting step.

Investigating the current runtime state is a general troubleshooting step for operational issues, but not specifically focused on troubleshooting the *upload process* of firmware.

Investigating damaged hardware is a hardware-level troubleshooting step, which is distinct from issues directly related to the *firmware upload process* itself.

Reviewing the configuration history allows administrators to compare configurations before and after a firmware upgrade, or to revert to a previous working configuration if the new firmware introduces problems.