Configuration properties in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are configuration properties in cloud infrastructure?

Configuration properties are settings that define how cloud resources behave and interact. They control things like resource size, network settings, and security options.

beginner

Why is it important to manage configuration properties carefully?

Because incorrect settings can cause resources to fail, become insecure, or cost more. Proper management ensures resources work as expected and stay safe.

intermediate

How can you change configuration properties in Google Cloud Platform (GCP)?

You can change them using the GCP Console, gcloud command-line tool, or Infrastructure as Code tools like Terraform.

beginner

What is a real-life example of a configuration property in GCP?

For a Compute Engine VM, a configuration property could be the machine type (like n1-standard-1), which decides the CPU and memory size.

intermediate

What is the benefit of using Infrastructure as Code (IaC) for configuration properties?

IaC lets you write configuration as code, making it easy to track changes, reuse setups, and deploy resources consistently.

Which tool can you use to change configuration properties in GCP?

A Slack

B Microsoft Word

C gcloud command-line tool

D Adobe Photoshop

The gcloud command-line tool is designed to manage GCP resources and their configuration properties.

What does a configuration property control?

A The color of your computer screen

B How a cloud resource behaves

C Your internet speed

D The weather forecast

Configuration properties define the behavior and settings of cloud resources.

Why use Infrastructure as Code for configuration?

A To write configuration as code for easy reuse and tracking

B To draw pictures of cloud resources

C To play music

D To send emails

Infrastructure as Code helps automate and manage configurations reliably.

Which of these is an example of a configuration property for a VM in GCP?

A Machine type (CPU and memory size)

B Screen brightness

C Keyboard layout

D Mouse speed

Machine type defines the CPU and memory for a VM, which is a key configuration property.

What happens if configuration properties are set incorrectly?

A Your phone battery lasts longer

B Nothing changes

C You get free cloud credits

D Resources may fail or become insecure

Incorrect settings can cause failures or security risks in cloud resources.

Explain what configuration properties are and why they matter in cloud infrastructure.

Think about how settings control a device or appliance in your home.

Describe how you can manage configuration properties in Google Cloud Platform.

Consider both graphical and code-based methods.

Practice

1. What is the purpose of configuration properties in Google Cloud Platform (GCP)?

easy

A. To define settings that control how cloud resources behave

B. To write application code for cloud functions

C. To store user data in databases

D. To monitor network traffic in real-time

Solution

1. Step 1: Understand configuration properties

   Configuration properties are settings that control the behavior of cloud resources like virtual machines, storage, or services.

2. Step 2: Differentiate from other cloud tasks

   Writing code, storing data, or monitoring traffic are different tasks not directly related to configuration properties.

3. Final Answer:

   To define settings that control how cloud resources behave -> Option A

4. Quick Check:

   Configuration properties = settings control behavior [OK]

Hint: Think of configuration as setting rules for cloud resources [OK]

Common Mistakes:

• Confusing configuration with coding
• Mixing configuration with data storage
• Assuming configuration monitors traffic

2. Which of the following is the correct way to specify a configuration property in a GCP YAML deployment file?

easy

A. config:
instanceType = n1-standard-1

B. properties:
instanceType: n1-standard-1

C. settings:
instanceType: 'n1-standard-1'

D. parameters:
instanceType -> n1-standard-1

Solution

1. Step 1: Identify correct YAML syntax for properties

   In GCP deployment manager, configuration properties are under 'properties:' with key-value pairs using colon and indentation.

2. Step 2: Check each option's syntax

   properties: instanceType: n1-standard-1 uses 'properties:' and colon syntax correctly. Options B, C, and D use incorrect keys or invalid syntax like '=' or '->'.

3. Final Answer:

   properties: instanceType: n1-standard-1 -> Option B

4. Quick Check:

   YAML properties use colon and indentation [OK]

Hint: YAML uses colon and indentation for key-value pairs [OK]

Common Mistakes:

• Using '=' instead of ':' in YAML
• Wrong top-level key like 'config' or 'settings'
• Using symbols like '->' which are invalid in YAML

3. Given this snippet of a GCP deployment YAML:

resources:
- name: my-vm
  type: compute.v1.instance
  properties:
    zone: us-central1-a
    machineType: zones/us-central1-a/machineTypes/n1-standard-1
    disks:
    - deviceName: boot
      type: PERSISTENT
      boot: true
      autoDelete: true
      initializeParams:
        sourceImage: projects/debian-cloud/global/images/family/debian-10

What is the machine type configured for the VM?

medium

A. n1-standard-1

B. us-central1-a

C. debian-10

D. PERSISTENT

Solution

1. Step 1: Locate machineType property

   The machineType is set under properties as 'zones/us-central1-a/machineTypes/n1-standard-1'. The last part after the last slash is the machine type.

2. Step 2: Extract machine type value

   The machine type is 'n1-standard-1', which defines the VM size and resources.

3. Final Answer:

   n1-standard-1 -> Option A

4. Quick Check:

   Machine type is the last part of the path [OK]

Hint: Machine type is the last segment in the machineTypes path [OK]

Common Mistakes:

• Confusing zone with machine type
• Picking image name as machine type
• Selecting disk type as machine type

4. You have this GCP deployment YAML snippet:

resources:
- name: my-storage
  type: storage.v1.bucket
  properties:
    location: us-east1
    storageClass: STANDARD
    versioning:
      enabled: true
    accessControl:
      - entity: allUsers
        role: READER

What is the error in this configuration?

medium

A. location must be a zone, not a region

B. versioning.enabled must be false for public buckets

C. accessControl should be acl

D. storageClass must be lowercase

Solution

1. Step 1: Check property names for storage bucket

   The correct property for access control in GCP storage buckets is 'acl', not 'accessControl'.

2. Step 2: Validate other properties

   Versioning can be true or false regardless of public access. StorageClass is case-insensitive but usually uppercase is accepted. Location is a region, which is correct.

3. Final Answer:

   accessControl should be acl -> Option C

4. Quick Check:

   Property names must match GCP specs exactly [OK]

Hint: Check exact property names in GCP docs [OK]

Common Mistakes:

• Using incorrect property name 'accessControl' instead of 'acl'
• Assuming versioning must be false for public buckets
• Confusing region and zone names

5. You want to configure a GCP Compute Engine instance with a startup script and custom metadata. Which configuration properties should you use in your deployment YAML to achieve this?

hard

A. startupScript: |
#!/bin/bash
echo Hello World

B. scripts:
startup: '#!/bin/bash\necho Hello World'

C. customMetadata:
startup-script: '#!/bin/bash\necho Hello World'

D. metadata:
items:
- key: startup-script
value: |-
#!/bin/bash
echo Hello World

Solution

1. Step 1: Identify correct metadata property for startup scripts

   GCP Compute Engine uses 'metadata' with 'items' list containing key-value pairs for custom metadata like 'startup-script'.

2. Step 2: Verify syntax for multiline script

   Using '|-' in YAML allows multiline script values correctly under 'value'. Other options use incorrect property names or formats.

3. Final Answer:

   metadata: items: - key: startup-script value: |- #!/bin/bash echo Hello World -> Option D

4. Quick Check:

   Use metadata.items with key startup-script [OK]

Hint: Startup scripts go under metadata.items with key 'startup-script' [OK]

Common Mistakes:

• Using wrong property names like startupScript or scripts
• Not formatting multiline scripts properly in YAML
• Placing script outside metadata block