Build triggers configuration in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Trigger Behavior on Branch Push

You configure a Cloud Build trigger to start a build when code is pushed to the 'main' branch. What happens if a push is made to the 'develop' branch?

A The build trigger activates and starts a build.

B The build trigger activates but the build fails immediately.

C The build trigger does not activate; no build starts.

D The build trigger activates only if the commit message contains 'build'.

💡 Hint

Triggers can be set to watch specific branches only.

A build trigger configured for the 'main' branch only activates when code is pushed to 'main'. Pushes to other branches like 'develop' do not start builds.

❓ Configuration

intermediate

YAML Trigger Configuration for Tag Push

Which YAML snippet correctly configures a Cloud Build trigger to start a build only when a tag matching 'v*' is pushed?

A

triggerTemplate:
  repoName: my-repo
  branchName: 'main'

B

triggerTemplate:
  repoName: my-repo
  branchName: 'v*'

C

triggerTemplate:
  repoName: my-repo
  tagName: 'release-*'

D

triggerTemplate:
  repoName: my-repo
  tagName: 'v*'

💡 Hint

Tags and branches use different fields in trigger configuration.

The 'tagName' field specifies tag patterns. 'v*' matches tags starting with 'v'. 'branchName' is for branches, so option D is incorrect. Option D uses a different tag pattern.

❓ Architecture

advanced

Best Trigger Setup for Multiple Environments

You have three environments: dev, staging, and production. You want builds to trigger automatically on pushes to branches 'dev', 'staging', and 'main' respectively, each deploying to its environment. What is the best way to configure Cloud Build triggers?

A Create one trigger watching all branches and use build steps to deploy based on branch name.

B Create three separate triggers, each watching one branch and deploying to its environment.

C Create one trigger watching the 'main' branch and manually deploy dev and staging builds.

D Create triggers only for 'main' and 'staging' branches; dev builds run manually.

💡 Hint

Separate triggers simplify environment-specific builds and deployments.

Having separate triggers for each branch allows clear separation of build and deployment logic per environment, reducing complexity and risk.

❓ security

advanced

Securing Build Triggers from Unauthorized Changes

How can you prevent unauthorized users from modifying Cloud Build triggers in a shared project?

A Use IAM to restrict 'Cloud Build Admin' role only to trusted users.

B Grant all users the 'Cloud Build Editor' role.

C Disable triggers and run builds manually.

D Store trigger configurations in a public GitHub repo.

💡 Hint

Control permissions carefully with IAM roles.

Only trusted users should have 'Cloud Build Admin' role to create or modify triggers. Granting broad editor roles or making configs public risks unauthorized changes.

✅ Best Practice

expert

Optimizing Build Trigger Performance

You notice your Cloud Build triggers start builds for every commit, causing long queues and high costs. Which configuration change best reduces unnecessary builds?

A Configure triggers to only activate on changes to specific paths or files.

B Increase the number of concurrent builds allowed.

C Disable triggers and run builds on a schedule.

D Use a single trigger for all branches without filters.

💡 Hint

Filtering triggers by file changes reduces builds.

By configuring triggers to only start builds when certain files or directories change, you avoid builds for irrelevant commits, improving efficiency and cost.