Certificate Authority Service in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Certificate Authority in Google Cloud.

GCP

gcloud privateca certificate-authorities create my-ca --location=[1] --pool=my-pool

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

Asouthamerica-east1

Beurope-west1

Casia-east1

Dus-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a region where the service is not available.

Leaving the location blank.

The us-central1 region is commonly used for creating Certificate Authorities in Google Cloud. This command sets the location for the CA.

2fill in blank

medium

Complete the code to issue a new certificate from an existing Certificate Authority.

GCP

gcloud privateca certificates create my-cert --certificate-authority=my-ca --location=us-central1 --certificate-config=[1]

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

Aconfig.yaml

Bconfig.json

Cconfig.txt

Dconfig.xml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a YAML or XML file instead of JSON.

Using a text file without proper JSON structure.

The certificate configuration is typically provided in a JSON file. Here, config.json is the correct format for the certificate config.

3fill in blank

hard

Fix the error in the command to revoke a certificate by completing the missing flag.

GCP

gcloud privateca certificates revoke my-cert --certificate-authority=my-ca --location=us-central1 [1]=KEY_COMPROMISE

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

A--reason

B--cause

C--status

D--type

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect flags like --cause or --type.

Omitting the reason flag entirely.

The --reason flag specifies why the certificate is revoked. KEY_COMPROMISE is a valid reason.

4fill in blank

hard

Fill both blanks to create a certificate revocation list (CRL) and specify its maximum size.

GCP

gcloud privateca crl-pools create my-crl-pool --location=us-central1 --max-entries=[1] --description=[2]

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

A1000

B500

C"CRL for revoked certificates"

D"Certificate revocation list"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a small number for max entries.

Not quoting the description string.

The --max-entries flag sets the maximum number of entries in the CRL. 1000 is a common limit. The --description flag provides a description, here "CRL for revoked certificates".

5fill in blank

hard

Fill all three blanks to define a certificate template with a specific key algorithm, key usage, and lifetime.

GCP

gcloud privateca templates create my-template --location=us-central1 --key-algorithm=[1] --key-usage=[2] --lifetime=[3]

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

ARSA_2048

Bdigital_signature

C8760h

DECDSA_P256

Attempts:

3 left

💡 Hint

Common Mistakes

Using RSA instead of ECDSA for key algorithm.

Using incorrect key usage values.

Setting lifetime in wrong units.

The --key-algorithm is set to ECDSA_P256 for a secure elliptic curve key. The --key-usage is digital_signature to allow signing. The --lifetime is 8760h, which equals one year.

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