Your DevOps engineering team is configuring an automated continuous integration pipeline using Cloud Build for an application repository hosted on GitLab. You must configure a Cloud Build trigger that meets the following criteria: Initiates builds on merge requests (pull requests) that target release branches matching patterns such as release/v1.0 or release/v2.4. Prevents unauthorized build resource consumption by requiring repository owners or collaborators to approve merge requests from external contributors using the /gcbrun comment command before a build executes. Ensures proper architectural alignment between the trigger and the GitLab repository connection in Google Cloud. How should you configure the Cloud Build trigger?

Set the trigger Event to 'Pull request', specify the target branch regex as '^release/v[0-9]+\.[0-9]+$' using RE2 syntax, select 'Required except for owners and collaborators' for Comment control, and ensure the trigger region matches the repository connection region.: ### What Cloud Build VCS Triggers with Comment Control Are **Cloud Build triggers** integrated with external version control systems like **GitLab** and **GitHub** automate build execution based on repository events such as branch pushes, tag creations, or pull and merge requests. When connected via Developer Connect or 2nd generation repository connections, triggers utilize **RE2 regular expression syntax** to filter target branches or tags and offer granular **comment control** settings to safeguard build environments against unverified code execution. ### How It Meets the Requirements - **Targeting Release Branches**: Cloud Build evaluates branch and tag filters using **RE2 regular expression syntax**. The expression `^release/v[0-9]+\.[0-9]+$` accurately matches branches formatted as `release/v1.0` or `release/v2.4` while preventing accidental invocation from non-matching feature branches. - **Securing External Contributions**: The **Comment control** setting `Required except for owners and collaborators` allows trusted project members to trigger builds automatically on merge requests while forcing external contributors' merge requests to wait until an authorized collaborator reviews the changes and comments `/gcbrun`. - **Regional Configuration**: Cloud Build repository connections (such as Developer Connect connections for GitLab) require that the **trigger region** strictly matches the **region of the repository connection**. ### Key Advantages and Capabilities - **Secure Pipeline Automation**: Prevents arbitrary and potentially malicious code from running in privileged build infrastructure without peer review. - **Strict Pattern Matching**: RE2 regex support allows precise branch and tag targeting without unexpected execution on unrelated branches. - **Native SCM Integration**: Automatically reports build status, commits, and logs back to the GitLab merge request UI. - **Resource and Cost Protection**: Avoids unnecessary concurrency usage and infrastructure costs by gating untrusted merge requests. ### Why This Is Optimal This configuration directly satisfies all operational, security, and architectural constraints by combining native RE2 branch targeting, regional alignment, and automated collaborator comment gating without introducing third-party webhook middleware.

Cloud Build Gitlab Trigger Regex Comment Control | Professional Cloud DevOps Engineer

Cloud Build Gitlab Trigger Regex Comment Control

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your DevOps engineering team is configuring an automated continuous integration pipeline using Cloud Build for an application repository hosted on GitLab.

You must configure a Cloud Build trigger that meets the following criteria:

Initiates builds on merge requests (pull requests) that target release branches matching patterns such as release/v1.0 or release/v2.4.
Prevents unauthorized build resource consumption by requiring repository owners or collaborators to approve merge requests from external contributors using the /gcbrun comment command before a build executes.
Ensures proper architectural alignment between the trigger and the GitLab repository connection in Google Cloud.

How should you configure the Cloud Build trigger?

Set the trigger Event to 'Pull request', specify the branch filter with a PCRE lookahead pattern, configure Comment control to 'Required' for all contributors, and set the trigger region to 'global'.

Set the trigger Event to 'Pull request', specify the target branch regex as '^release/v[0-9]+.[0-9]+$', configure Comment control to 'Not required', and create an Eventarc trigger to route merge request webhooks.

Set the trigger Event to 'Pull request', specify the target branch regex as '^release/v[0-9]+.[0-9]+$' using RE2 syntax, select 'Required except for owners and collaborators' for Comment control, and ensure the trigger region matches the repository connection region.

Set the trigger Event to 'Push to a branch', configure the branch pattern as 'release/v*.*', set Comment control to 'Not required', and set the trigger region to 'global'.

Professional Cloud DevOps Engineer

Cloud Build Gitlab Trigger Regex Comment Control

Related questions