Leaks and backups

Questions 1 to 5 of 8

1. 1. Put these steps in the order the lesson gives for rotating a leaked key.

   Use the arrows to put the steps in order.

   1. 1.Revoke the old key, so that requests made with it are refused↑↓
   2. 2.Review the provider's logs for use of the old key↑↓
   3. 3.Store the new key where the app reads it, then deploy or restart the app and check that it works↑↓
   4. 4.Create a new key in the provider's dashboard, and keep the old key active for now↑↓
2. 2. Put these steps in the order the backup script in worked example 2 runs them.

   Use the arrows to put the steps in order.

   1. 1.Copy the archive to a second drive and to an off-site folder↑↓
   2. 2.Restore each of the three archives into a test folder↑↓
   3. 3.Compare every restored file with the source, using a checksum for each file↑↓
   4. 4.Pack the source folder into a dated archive↑↓
3. 3. A key is committed in config.py. A later commit deletes the file. Where is the key now?

   Only in the newest commit, which no longer has the fileNowhere, because the deletion removes the key from every commitIn the older commits and in every copy of the repo made before the fixOnly on the developer's laptop, not in the hosting service
4. 4. What does this program print? ``python import re line = 'PAYMENT_API_KEY = "sk_test_EXAMPLE0000000000000000"' print(bool(re.search(r'sk_(test|live)_[A-Za-z0-9]+', line))) ``

   TrueFalseNoneThe line, unchanged
5. 5. Adding config.py to .gitignore after it was committed stops git from tracking the file.

   True, because .gitignore hides every listed file from git, including files already committedFalse, because .gitignore only applies to files git does not track yet, so a committed file stays tracked