Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise manages three separate Google Cloud environments (development, staging, and production) deployed across distinct GCP projects. The security team requires uniform Sensitive Data Protection (Cloud DLP) inspection rules—such as scanning for national identifiers, credentials, and sensitive customer data—across storage repositories in all environments. Currently, individual teams define inline inspection configurations inside their local continuous integration and continuous deployment (CI/CD) pipelines, which has caused severe configuration drift and high operational maintenance.
You need to implement a declarative Infrastructure as Code (IaC) configuration architecture that enforces standardized inspection policies across all environments, isolates deployment states, and allows policy updates without modifying downstream jobs. What should you do?
InspectConfig payloads inside each environment's Terraform state file and repository, requiring each team to independently update their configurations.An inline InspectConfig defines inspection rules directly inside an individual API call, Cloud Function, or pipeline configuration file without utilizing reusable Sensitive Data Protection template objects.
development, staging, and production repositories creates duplicate definitions. As teams make local changes, configuration drift inevitably occurs.InspectConfig) with the data execution job (inspectJob).The organization had only a single non-production project with one-off, ad-hoc scanning requirements where creating centralized templates would add unnecessary administrative overhead.
Using inline configurations violates Infrastructure as Code best practices for multi-tenant and multi-environment architectures because it fails to establish a single source of truth.
InspectTemplate resources at the organization level with dedicated state isolation, and configure environment-specific scan jobs to reference the organization template ID.An InspectTemplate in Google Cloud's Sensitive Data Protection (Cloud DLP) service is a reusable configuration object that encapsulates inspection parameters, including built-in infoTypes, custom regex detectors, and likelihood thresholds. When created at the organization level (organizations/{org_id}/inspectTemplates), the template acts as a single, canonical policy definition that is accessible across all projects in the resource hierarchy.
InspectTemplate ensures that development, staging, and production environments execute the exact same detection logic.Centralized declarative templates combined with isolated state storage represent the Google Cloud recommended architecture for multi-environment governance. It ensures strict policy enforcement, prevents state locks or corruption across environments, and eliminates duplicate configuration maintenance.
InspectTemplate resources across all projects using a single monolithic Terraform state file shared across development, staging, and production.A monolithic Terraform state file stores the infrastructure state of all environments (development, staging, and production) in a single global backend state storage object, while deploying duplicate project-level InspectTemplate resources in each environment.
projects/{project_id}/inspectTemplates) instead of organization-level templates requires modifying multiple template instances whenever security requirements change.The cloud environment consisted of a single isolated project with no shared resources, where managing cross-project organization templates was unsupported or restricted.
Best practices for declarative configuration mandate separating backend state files by environment and layer (e.g., foundation, security, application) to guarantee isolation.
DeidentifyTemplate at the organization level, and configure each environment's pipeline to apply de-identification transformations directly during storage scans.A DeidentifyTemplate is a Sensitive Data Protection resource designed to save configuration information for data transformation and masking jobs. It specifies structured dataset transformations, such as masking, bucketing, cryptographic hashing, or tokenization of sensitive infoTypes.
InspectTemplate, not a DeidentifyTemplate.DeidentifyConfig object rather than InspectConfig.The primary objective was to enforce uniform cryptographic pseudonymization or data masking across database exports moving from production into lower environments like staging and development.
In Sensitive Data Protection, InspectTemplate and DeidentifyTemplate serve complementary but distinct roles: inspection discovers sensitive findings, while de-identification transforms sensitive findings.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated