Cloud KMS for key management in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new key ring in Cloud KMS.

GCP

gcloud kms keyrings create [1] --location=us-central1

Drag options to blanks, or click blank then click option'

Amy-keyring

Bcreate-keyring

Ckeyring-create

Dnew-keyring

Attempts:

3 left

💡 Hint

Common Mistakes

Using command-like names instead of a simple key ring name.

Omitting the location parameter.

The command gcloud kms keyrings create my-keyring --location=us-central1 creates a key ring named my-keyring in the specified location.

2fill in blank

medium

Complete the code to create a new symmetric encryption key in the key ring.

GCP

gcloud kms keys create [1] --location=us-central1 --keyring=my-keyring --purpose=encryption

Drag options to blanks, or click blank then click option'

Amy-symmetric-key

Bsymmetric-create

Ckey-encrypt

Dencrypt-key

Attempts:

3 left

💡 Hint

Common Mistakes

Using verbs or commands as key names.

Not specifying the purpose correctly.

The command creates a symmetric encryption key named my-symmetric-key in the my-keyring key ring.

3fill in blank

hard

Fix the error in the command to encrypt data using the key.

GCP

echo 'Hello World' | gcloud kms encrypt --location=us-central1 --keyring=my-keyring --key=[1] --plaintext-file=- --ciphertext-file=encrypted.txt

Drag options to blanks, or click blank then click option'

Amy-keyring

Bencrypt-key

Cmy-symmetric-key

Dus-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the key ring name instead of the key name.

Using the location instead of the key name.

The --key flag requires the name of the key, which is my-symmetric-key. Using other values causes errors.

4fill in blank

hard

Fill both blanks to decrypt the ciphertext file and output the plaintext.

GCP

gcloud kms decrypt --location=us-central1 --keyring=[1] --key=[2] --ciphertext-file=encrypted.txt --plaintext-file=decrypted.txt

Drag options to blanks, or click blank then click option'

Amy-keyring

Bmy-symmetric-key

Cencrypt-key

Ddecrypt-key

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping key ring and key names.

Using incorrect key names.

The command uses the key ring my-keyring and the key my-symmetric-key to decrypt the file.

5fill in blank

hard

Fill all three blanks to list all keys in a key ring with their purpose.

GCP

gcloud kms keys list --location=[1] --keyring=[2] --format='table(name, [3])'

Drag options to blanks, or click blank then click option'

Aus-central1

Bmy-keyring

Cpurpose

DcreationTime

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong location or key ring names.

Choosing a wrong field in the format option.

This command lists all keys in the my-keyring key ring located in us-central1, showing their names and purposes.

Practice

1. What is the main purpose of Google Cloud KMS (Key Management Service)?

easy

A. To securely store and manage encryption keys

B. To host virtual machines

C. To manage user identities

D. To monitor network traffic

Solution

1. Step 1: Understand the role of Cloud KMS

   Cloud KMS is designed to store and manage encryption keys securely in the cloud.

2. Step 2: Compare with other services

   Hosting virtual machines, managing identities, and monitoring traffic are handled by other GCP services, not KMS.

3. Final Answer:

   To securely store and manage encryption keys -> Option A

4. Quick Check:

   Cloud KMS = key management [OK]

Hint: Cloud KMS is about keys, not machines or users [OK]

Common Mistakes:

• Confusing KMS with Compute Engine
• Thinking KMS manages users
• Assuming KMS monitors networks

2. Which of the following is the correct command to create a key ring named my-key-ring in location us-central1 using gcloud CLI?

easy

A. gcloud kms keyrings create my-key-ring --location=us-central1

B. gcloud kms create keyring my-key-ring --region=us-central1

C. gcloud kms keyrings new my-key-ring --location=us-central1

D. gcloud kms keyring create my-key-ring --zone=us-central1

Solution

1. Step 1: Recall gcloud syntax for key ring creation

   The correct command uses 'gcloud kms keyrings create' with the --location flag.

2. Step 2: Verify option details

   gcloud kms keyrings create my-key-ring --location=us-central1 matches the correct syntax and uses the correct flag '--location=us-central1'. Other options use wrong verbs or flags.

3. Final Answer:

   gcloud kms keyrings create my-key-ring --location=us-central1 -> Option A

4. Quick Check:

   Correct gcloud syntax = gcloud kms keyrings create my-key-ring --location=us-central1 [OK]

Hint: Use 'keyrings create' with --location flag for key rings [OK]

Common Mistakes:

• Using --region instead of --location
• Wrong command order like 'create keyring'
• Using --zone which is for compute resources

3. Given the following Python snippet using Google Cloud KMS client, what will be the output if the key does not exist?

from google.cloud import kms_v1
client = kms_v1.KeyManagementServiceClient()
key_name = client.crypto_key_path('my-project', 'us-central1', 'my-key-ring', 'nonexistent-key')
response = client.get_crypto_key(request={'name': key_name})
print(response.name)

medium

A. Prints the key name string

B. Raises a NotFound exception

C. Prints None

D. Returns an empty response object

Solution

1. Step 1: Understand get_crypto_key behavior

   When requesting a key that does not exist, the client raises a NotFound error.

2. Step 2: Check the code flow

   The code calls get_crypto_key with a nonexistent key name, so it will not print but raise an exception.

3. Final Answer:

   Raises a NotFound exception -> Option B

4. Quick Check:

   Missing key triggers NotFound error [OK]

Hint: Missing keys cause NotFound exceptions, not None [OK]

Common Mistakes:

• Assuming it prints the key name anyway
• Expecting None instead of error
• Thinking it returns empty object

4. You try to rotate a key in Cloud KMS using the command:

gcloud kms keys rotate my-key --keyring=my-key-ring --location=us-central1

But you get an error. What is the most likely cause?

medium

A. The key is already rotated

B. The location flag is misspelled

C. The key ring does not exist

D. The key does not have rotation policy set

Solution

1. Step 1: Understand prerequisites for key rotation

   The keyring must exist in the specified location before you can perform operations like rotating a key in it.

2. Step 2: Analyze the error cause

   If the key ring does not exist, the command fails with a resource not found error. Manual rotation does not require a rotation policy, the location flag is correct, and keys can be rotated multiple times.

3. Final Answer:

   The key ring does not exist -> Option C

4. Quick Check:

   Keyring must exist for key rotation [OK]

Hint: Create keyring before rotating keys [OK]

Common Mistakes:

• Thinking rotation policy is required
• Believing key can't be rotated if already rotated
• Assuming location flag typo

5. You want to ensure your encryption keys in Cloud KMS are rotated automatically every 30 days. Which configuration should you apply to the key to achieve this?

hard

A. Set the key ring's location to a region that supports auto-rotation

B. Manually run the rotate command every 30 days

C. Create a new key every 30 days and delete the old one

D. Set the key's rotation period to 30 days using the --rotation-period flag

Solution

1. Step 1: Understand automatic rotation in Cloud KMS

   Automatic rotation is configured by setting the key's rotation period property.

2. Step 2: Evaluate options

   Set the key's rotation period to 30 days using the --rotation-period flag correctly sets the rotation period. Manual rotation or creating new keys are manual processes. Location does not control rotation.

3. Final Answer:

   Set the key's rotation period to 30 days using the --rotation-period flag -> Option D

4. Quick Check:

   Rotation period config enables automatic key rotation [OK]

Hint: Use --rotation-period to automate key rotation [OK]

Common Mistakes:

• Relying on manual rotation only
• Confusing key ring location with rotation
• Deleting and recreating keys unnecessarily