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 uses Google Cloud continuous integration and continuous delivery (CI/CD) pipelines to deploy microservices onto Google Kubernetes Engine (GKE) clusters. Following a security incident, the DevOps and security teams require a centralized auditing mechanism to trace all active and historical cluster deployments directly to their originating source code Git commit SHA, container artifact URI, and software package versions.
You need to implement a solution that captures this deployment metadata and allows you to programmatically inspect and analyze these audit records within Cloud Logging. What should you do?
This solution relies on Cloud Service Mesh authorization audit logging and Envoy access logs (server-accesslog-stackdriver) to monitor network traffic and policy evaluation between services in a service mesh.
logging?rbac=debug), adding unnecessary compute and logging overhead.You needed to audit whether unauthorized microservices were attempting to communicate across namespaces in violation of mesh authorization policies.
Developer Connect insights is a Google Cloud capability that correlates software delivery lifecycle (SDLC) metadata—such as source code revisions, build artifacts, and package dependencies—with running deployment workloads across environments. It automatically persists these deployment insights into Cloud Logging as structured log entries.
commitReferences (including the exact commitSha and commit URL) and the target artifactUri in Artifact Registry.artifactDetails.packages, providing package names and package versions (e.g., specific library builds) included in the deployment.projects/PROJECT_ID/logs/developerconnect.googleapis.com/sdlc_deployment. Teams can query them via the Cloud Logging API, Logs Explorer, or the gcloud logging read command using structured filters such as labels.insights_config_id.Developer Connect insights provides fully managed, out-of-the-box extraction and correlation of SDLC metadata directly into structured Cloud Logging entries. It removes the operational burden of writing custom webhook interceptors or parsing custom build manifests manually across multiple pipelines.
This approach uses Cloud Data Fusion IAM roles (roles/datafusion.viewer) and API methods (datafusion.pipelines.get) to inspect ETL/ELT data integration pipeline execution states.
datafusion.pipelines.get method retrieves metadata about data pipelines (such as ETL transformations, source endpoints, and sink datasets), not software source code commit SHAs, container images, or application package dependencies.Your team needed to audit the execution history and structure of enterprise ETL data transformation jobs in Cloud Data Fusion.
This approach uses the Cloud Deploy Viewer (roles/clouddeploy.viewer) IAM role and inspects Cloud Audit Logs for calls to the clouddeploy.deliveryPipelines.listEffectiveTags method to track resource metadata.
clouddeploy.deliveryPipelines.listEffectiveTags method and its corresponding audit logs only evaluate resource tags attached to the delivery pipeline resource itself for IAM policy inheritance and governance. They do not record Git commit SHAs, source repository URLs, or software package dependencies.roles/clouddeploy.viewer is a read-only role granting permissions like clouddeploy.deliveryPipelines.list and clouddeploy.releases.get, but it does not generate deep dependency inspection logs.You needed to grant read-only access to an auditor to evaluate organizational resource hierarchy tags attached to Cloud Deploy delivery pipeline resources.
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