Check: secrets | ComputeSphere Learn

Goal: Confirm you can spot a secret, name how it leaks, respond to a leak in the right order, and give each environment its own configuration.

Four questions: three on Module 6 and one from Module 4. Every answer explains itself, right or wrong.

Which of these values should be stored as a secret?PAYMENTS_URL=https://payments.example.comWEBHOOK_SIGNING_SECRET, used to check that webhooks came from your payment providerA public key your app uses to verify signatures

Your app prints its whole configuration when it starts, to help with debugging. Which leak path is that?LogsGitImages

You find a real API key in a commit from last week. In what order do you act?Rewrite the history, force-push, then rotate the keyRotate the key and revoke the old one, then clean the historyDelete it in a new commit; rotation isn't needed if the repository is private

From Module 4: your app works locally, and production needs a different database. What should change between the two?A separate build for production with the URL written inOnly the DATABASE_URL the app is given when it startsA config.production.json committed next to the code

Retry as often as you like.