Bird
Raised Fist0
GCPcloud~10 mins

Configuration properties in GCP - Interactive Code Practice

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to set the project ID in the configuration.

GCP
gcloud config set project [1]
Drag options to blanks, or click blank then click option'
Amy-project-123
B--project
Cproject-id
Dset-project
Attempts:
3 left
💡 Hint
Common Mistakes
Using flags like --project instead of the project ID.
Typing 'project-id' literally instead of the actual project name.
2fill in blank
medium

Complete the command to set the default compute zone in gcloud configuration.

GCP
gcloud config set compute/[1] us-central1-a
Drag options to blanks, or click blank then click option'
Azone
Bregion
Clocation
Darea
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'region' instead of 'zone'.
Using incorrect property names like 'location' or 'area'.
3fill in blank
hard

Fix the error in the command to set the default compute region.

GCP
gcloud config set compute/[1] us-central1
Drag options to blanks, or click blank then click option'
Azone
Blocation
Carea
Dregion
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'zone' instead of 'region'.
Using invalid property names like 'location' or 'area'.
4fill in blank
hard

Fill both blanks to configure the default account and project.

GCP
gcloud config set [1] user@example.com
gcloud config set [2] my-project-123
Drag options to blanks, or click blank then click option'
Aaccount
Buser
Cproject
Ddefault
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'user' instead of 'account'.
Using 'default' instead of 'project'.
5fill in blank
hard

Fill all three blanks to list all current gcloud configuration properties.

GCP
gcloud [1] list --[2] --format=[3]
Drag options to blanks, or click blank then click option'
Aget
Ball
Cyaml
Dconfig
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'get' instead of 'list'.
Using '--all' incorrectly or missing it.
Not specifying the output format.

Practice

(1/5)
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