Certificate Authority Service in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Certificate Authority Service in cloud infrastructure?

It issues and manages digital certificates that help secure communication by verifying identities, like a trusted notary for websites and services.

beginner

How does a digital certificate help secure communication?

It proves the identity of a website or service and enables encrypted connections, so data stays private and safe from eavesdroppers.

intermediate

What is a root certificate in a Certificate Authority Service?

A root certificate is the top-level trusted certificate that signs other certificates, like the main stamp of approval in a chain of trust.

intermediate

Why is it important to rotate certificates regularly?

Rotating certificates reduces the risk of compromise by limiting how long a certificate is valid, similar to changing locks periodically for safety.

advanced

What role does the Certificate Authority Service play in a zero-trust security model?

It provides trusted certificates to verify every device and service continuously, ensuring only authorized entities communicate securely.

What does a Certificate Authority (CA) primarily do?

A Stores user passwords securely

B Monitors network traffic

C Issues and manages digital certificates

D Manages cloud storage buckets

A Certificate Authority issues and manages digital certificates that verify identities and enable secure communication.

Which certificate is at the top of the trust chain in a CA service?

A Intermediate certificate

B Client certificate

C Server certificate

D Root certificate

The root certificate is the top-level trusted certificate that signs other certificates in the chain.

Why should certificates be rotated regularly?

A To reduce risk of compromise

B To improve network speed

C To save storage space

D To increase certificate size

Regular rotation limits how long a certificate is valid, reducing the risk if it gets compromised.

In GCP, what is a common use of the Certificate Authority Service?

A Issuing SSL/TLS certificates for secure websites

B Configuring firewalls

C Creating databases

D Managing virtual machines

GCP's Certificate Authority Service is used to issue SSL/TLS certificates that secure websites and services.

What does a digital certificate contain?

A User passwords

B Public key and identity information

C Encrypted files

D Network logs

A digital certificate contains a public key and information about the identity it verifies.

Explain how a Certificate Authority Service helps secure communication in cloud environments.

Think about how websites prove they are safe to visit.

Describe the importance of certificate rotation and how it improves security.

Consider why you might change passwords or locks regularly.

Practice

1. What is the main purpose of the Certificate Authority Service in Google Cloud?

easy

A. To store large amounts of data securely

B. To create and manage digital certificates for secure communication

C. To monitor network traffic in real-time

D. To provide virtual machines for computing tasks

Solution

1. Step 1: Understand the role of Certificate Authority Service

   This service is designed to create and manage digital certificates that prove identity and secure communication.

2. Step 2: Compare with other options

   Options A, C, and D describe other cloud services unrelated to certificate management.

3. Final Answer:

   To create and manage digital certificates for secure communication -> Option B

4. Quick Check:

   Certificate Authority Service = Manage digital certificates [OK]

Hint: Remember: Certificate Authority = issues certificates [OK]

Common Mistakes:

• Confusing certificate management with data storage
• Thinking it monitors network traffic
• Assuming it provides computing resources

2. Which of the following is the correct way to create a self-signed certificate authority using gcloud CLI?

easy

A. gcloud privateca certificates create my-cert --issuer=my-root --location=us-central1

B. gcloud privateca subordinate create my-sub --subject="CN=My Sub CA" --location=us-central1

C. gcloud privateca roots create my-root --subject="CN=My Root CA" --pool=my-pool --location=us-central1

D. gcloud privateca revoke my-cert --location=us-central1

Solution

1. Step 1: Identify command for self-signed root CA creation

   The command gcloud privateca roots create is used to create a self-signed root certificate authority.

2. Step 2: Verify other options

   gcloud privateca subordinate create my-sub --subject="CN=My Sub CA" --location=us-central1 creates a subordinate CA, C creates a certificate, and D revokes a certificate, so they are incorrect for creating a self-signed CA.

3. Final Answer:

   gcloud privateca roots create my-root --subject="CN=My Root CA" --pool=my-pool --location=us-central1 -> Option C

4. Quick Check:

   Self-signed CA uses 'roots create' command [OK]

Hint: Self-signed CA uses 'roots create' command in gcloud [OK]

Common Mistakes:

• Using subordinate create command for root CA
• Confusing certificate creation with CA creation
• Trying to revoke instead of create

3. Given the following code snippet, what will be the output of the command?

gcloud privateca certificates list --location=us-central1 --ca-pool=my-pool

medium

A. Lists all certificates issued by the CA pool named 'my-pool' in us-central1

B. Deletes all certificates in the CA pool 'my-pool'

C. Creates a new certificate in the CA pool 'my-pool'

D. Shows the details of the CA pool 'my-pool' without certificates

Solution

1. Step 1: Understand the command purpose

   The command gcloud privateca certificates list lists certificates issued by a specified CA pool.

2. Step 2: Analyze parameters

   The parameters specify the location and the CA pool name, so the output will be the list of certificates issued by that pool in that location.

3. Final Answer:

   Lists all certificates issued by the CA pool named 'my-pool' in us-central1 -> Option A

4. Quick Check:

   Certificates list command outputs issued certificates [OK]

Hint: List command shows issued certificates, not create or delete [OK]

Common Mistakes:

• Thinking list deletes or creates certificates
• Confusing CA pool details with certificate list
• Ignoring the location parameter

4. You tried to create a subordinate CA with the command:

gcloud privateca subordinate create my-sub --pool=my-pool --issuer=my-root --location=us-central1

But got an error about missing permissions. What is the most likely cause?

medium

A. You do not have the required IAM role to create subordinate CAs

B. The command syntax is incorrect; 'subordinate create' is invalid

C. The location 'us-central1' does not support subordinate CAs

D. The issuer 'my-root' does not exist in the project

Solution

1. Step 1: Understand permission errors

   Permission errors usually mean the user lacks the required IAM role or permission to perform the action.

2. Step 2: Check command validity and other options

   The command syntax is valid, 'us-central1' supports subordinate CAs, and issuer existence errors usually mention not found, not permissions.

3. Final Answer:

   You do not have the required IAM role to create subordinate CAs -> Option A

4. Quick Check:

   Permission error = missing IAM role [OK]

Hint: Permission errors usually mean missing IAM role [OK]

Common Mistakes:

• Assuming syntax error causes permission issues
• Ignoring IAM roles and permissions
• Confusing location support with permission problems

5. You want to set up a secure internal network where your services trust certificates issued by your own CA. Which steps should you follow using Certificate Authority Service to achieve this?

hard

A. Create multiple root CAs and assign each service a different root CA

B. Create only a self-signed root CA and issue certificates directly from it to services

C. Use Google-managed CA and import your certificates manually to services

D. Create a root CA, create a subordinate CA signed by the root, then issue certificates from the subordinate CA to services

Solution

1. Step 1: Understand best practice for internal CA hierarchy

   Best practice is to create a root CA and then a subordinate CA signed by the root to issue certificates, improving security and manageability.

2. Step 2: Evaluate options

   Create only a self-signed root CA and issue certificates directly from it to services is less secure because issuing directly from root CA is discouraged. Use Google-managed CA and import your certificates manually to services uses Google-managed CA, not your own. Create multiple root CAs and assign each service a different root CA creates unnecessary complexity.

3. Final Answer:

   Create a root CA, create a subordinate CA signed by the root, then issue certificates from the subordinate CA to services -> Option D

4. Quick Check:

   Root CA + subordinate CA hierarchy = secure internal trust [OK]

Hint: Use root CA + subordinate CA for secure internal certificates [OK]

Common Mistakes:

• Issuing certificates directly from root CA
• Using Google-managed CA instead of own CA
• Creating multiple root CAs unnecessarily