Secret Manager for credentials in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of Secret Manager in Google Cloud?

Secret Manager securely stores sensitive information like passwords, API keys, and certificates, keeping them safe and easy to manage.

beginner

How does Secret Manager help avoid hardcoding credentials in your application?

It allows your app to fetch secrets at runtime securely, so credentials are not stored directly in code or configuration files.

intermediate

What is a 'secret version' in Secret Manager?

A secret version is a specific copy of the secret data. You can have multiple versions to update or roll back secrets safely.

intermediate

Which Google Cloud IAM role is needed to access secrets in Secret Manager?

The role 'Secret Manager Secret Accessor' allows users or services to read secret data securely.

intermediate

How does Secret Manager ensure your secrets remain secure during access?

It uses encryption at rest and in transit, and access is controlled by IAM policies to restrict who can view or manage secrets.

What is the best way to store API keys securely in Google Cloud?

A Use Secret Manager to store and access API keys

B Hardcode API keys in application source code

C Store API keys in a public Cloud Storage bucket

D Email API keys to team members

Secret Manager is designed to securely store sensitive data like API keys, avoiding insecure practices like hardcoding or public storage.

What does a secret version allow you to do?

A Automatically delete secrets after use

B Store secrets in different Google Cloud projects

C Share secrets publicly

D Keep multiple copies of a secret for updates and rollback

Secret versions let you manage changes safely by keeping multiple copies of secret data.

Which IAM role lets a service read secrets from Secret Manager?

A Network Admin

B Secret Manager Secret Accessor

C Compute Admin

D Storage Object Viewer

The 'Secret Manager Secret Accessor' role grants permission to read secret data.

How does Secret Manager protect secrets during storage?

A Requires manual encryption by users

B Stores secrets in plain text

C Encrypts secrets at rest and in transit

D Only encrypts secrets when accessed

Secret Manager automatically encrypts secrets both when stored and when sent over the network.

Why should you avoid hardcoding credentials in your app?

A It risks exposing secrets if code is shared or leaked

B It makes the app run slower

C It increases cloud costs

D It prevents the app from connecting to the internet

Hardcoding credentials risks accidental exposure, making Secret Manager a safer alternative.

Explain how Secret Manager helps keep your application credentials safe and easy to manage.

Think about how you would keep your house keys safe but accessible only to trusted people.

Describe the role of IAM in controlling access to secrets stored in Secret Manager.

Imagine giving different keys to different family members for different rooms.

Practice

1. What is the main purpose of Google Cloud Secret Manager?

easy

A. To host websites and web applications

B. To securely store and manage sensitive information like passwords and API keys

C. To analyze large datasets quickly

D. To create virtual machines for computing tasks

Solution

1. Step 1: Understand Secret Manager's role

   Secret Manager is designed to keep sensitive data safe and accessible only to authorized users.

2. Step 2: Compare options with Secret Manager's function

   Options A, C, and D describe other cloud services, not Secret Manager.

3. Final Answer:

   To securely store and manage sensitive information like passwords and API keys -> Option B

4. Quick Check:

   Secret Manager = Secure storage [OK]

Hint: Secret Manager = safe storage for secrets [OK]

Common Mistakes:

• Confusing Secret Manager with compute or storage services
• Thinking it hosts websites or runs code
• Assuming it analyzes data

2. Which command correctly creates a new secret named db-password in Secret Manager?

easy

A. gcloud secrets create db-password --replication-policy="automatic"

B. gcloud secret create db-password --auto-replication

C. gcloud secrets add db-password --replication=auto

D. gcloud create secret db-password --replication-policy=manual

Solution

1. Step 1: Recall correct gcloud syntax for creating secrets

   The correct command uses gcloud secrets create with the secret name and replication policy.

2. Step 2: Check each option's syntax

   gcloud secrets create db-password --replication-policy="automatic" matches the correct syntax exactly. Options A, B, and C have incorrect command structure or flags.

3. Final Answer:

   gcloud secrets create db-password --replication-policy="automatic" -> Option A

4. Quick Check:

   Correct command syntax = gcloud secrets create db-password --replication-policy="automatic" [OK]

Hint: Use 'gcloud secrets create' with replication policy [OK]

Common Mistakes:

• Using 'secret' instead of 'secrets' in command
• Wrong flag names like --auto-replication
• Incorrect command order or missing quotes

3. Given this Python code snippet accessing a secret version:

from google.cloud import secretmanager
client = secretmanager.SecretManagerServiceClient()
name = "projects/my-project/secrets/api-key/versions/latest"
response = client.access_secret_version(name=name)
payload = response.payload.data.decode("UTF-8")
print(payload)

What will this code print if the secret value is supersecret123?

medium

A. supersecret123

B. b'supersecret123'

C. api-key

D. projects/my-project/secrets/api-key/versions/latest

Solution

1. Step 1: Understand the code flow

   The code accesses the latest version of the secret named 'api-key' and decodes the binary data to a UTF-8 string.

2. Step 2: Determine the printed output

   Since payload.data is decoded, the output is the plain string 'supersecret123', not bytes or other values.

3. Final Answer:

   supersecret123 -> Option A

4. Quick Check:

   Decoded secret value = 'supersecret123' [OK]

Hint: Decoded secret data prints as plain string [OK]

Common Mistakes:

• Printing raw bytes without decoding
• Confusing secret name with secret value
• Expecting metadata instead of secret content

4. You try to access a secret but get a permission denied error. What is the most likely cause?

medium

A. The secret value is empty

B. The secret does not exist in the project

C. The secret version is disabled

D. The service account lacks the Secret Manager Secret Accessor role

Solution

1. Step 1: Analyze permission denied error context

   Permission denied usually means the caller lacks rights to access the secret.

2. Step 2: Identify required role for access

   The Secret Manager Secret Accessor role grants permission to read secret versions. Without it, access is denied.

3. Final Answer:

   The service account lacks the Secret Manager Secret Accessor role -> Option D

4. Quick Check:

   Permission denied = missing access role [OK]

Hint: Check service account roles for Secret Accessor permission [OK]

Common Mistakes:

• Assuming secret absence causes permission error
• Ignoring secret version state
• Thinking empty secret causes permission denied

5. You want to rotate a database password stored in Secret Manager without downtime. Which approach is best?

hard

A. Manually update the password in the database and Secret Manager at the same time

B. Delete the old secret and create a new secret with the new password

C. Create a new secret version with the new password and update your app to use the latest version

D. Store the password in a config file instead of Secret Manager

Solution

1. Step 1: Understand secret rotation best practice

   Adding a new secret version allows smooth transition without deleting old data, avoiding downtime.

2. Step 2: Evaluate options for zero downtime

   Create a new secret version with the new password and update your app to use the latest version uses versioning and app update to switch secrets seamlessly. Delete the old secret and create a new secret with the new password deletes data causing downtime. Manually update the password in the database and Secret Manager at the same time risks inconsistency. Store the password in a config file instead of Secret Manager is insecure.

3. Final Answer:

   Create a new secret version with the new password and update your app to use the latest version -> Option C

4. Quick Check:

   Rotate by adding new version, not deleting [OK]

Hint: Rotate secrets by adding versions, not deleting old ones [OK]

Common Mistakes:

• Deleting secrets causing downtime
• Updating database and secret separately risking mismatch
• Storing passwords insecurely outside Secret Manager