Which combination of steps will meet this requirement?
(Choose two.)
Stop the instance. Detach the root volume. Generate a new key pair.
Keep the instance running. Detach the root volume. Generate a new key pair.
When the volume is detached from the original instance, attach the volume to another instance as a data volume. Modify the authorized_keys file with a new public key. Move the volume back to the original instance. Start the instance.
When the volume is detached from the original instance, attach the volume to another instance as a data volume. Modify the authorized_keys file with a new private key. Move the volume back to the original instance. Start the instance.
When the volume is detached from the original instance, attach the volume to another instance as a data volume. Modify the authorized_keys file with a new public key. Move the volume back to the original instance that is running.
Explanations:
Stopping the instance and detaching the root volume allows for safe modification. Generating a new key pair prepares the security engineer to add a new public key for access recovery.
The instance must be stopped before detaching the root volume to avoid data corruption and ensure safe volume modification.
Attaching the volume to another instance and modifying the authorized_keys file with the new public key provides a way to regain SSH access.
Adding a new private key to the authorized_keys file is incorrect, as the authorized_keys file should contain only public keys for authentication.
Moving the modified volume back to the original instance requires the original instance to be stopped. Attaching it while running could lead to data inconsistency issues.