Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise wants to establish a comprehensive auditing and monitoring framework for user-managed service account keys across hundreds of projects in its Google Cloud organization. The security operations team has defined the following technical requirements:
Which combination of Google Cloud services and configurations should the security team deploy to satisfy these requirements?
iam.googleapis.com/ServiceAccountKey assets to assess key inventory and age; leverage IAM Policy Intelligence service account key insights to detect unused keys; and configure an organization-level aggregated Cloud Logging sink filtering for google.iam.admin.v1.CreateServiceAccountKey Admin Activity logs connected to Cloud Monitoring and Pub/Sub alerting.This architecture combines Cloud Asset Inventory, Policy Intelligence (IAM key insights/recommenders), and Cloud Logging aggregated sinks with Cloud Monitoring to establish full lifecycle visibility, inactivity detection, and real-time detection of user-managed service account key creation across an entire organization.
iam.googleapis.com/ServiceAccountKey reveals all existing user-managed keys, their associated service accounts, parent projects, and creation timestamps (validAfterTime).cloudaudit.googleapis.com/activity logs across all child folders and projects. Filtering for protoPayload.methodName="google.iam.admin.v1.CreateServiceAccountKey" captures all key creation events instantly and routes them to a Pub/Sub topic and Cloud Monitoring log-based alert for automated SOC notification.This approach uses Google Cloud-native governance and intelligence tools at the organization hierarchy root, ensuring zero blind spots across newly created or existing projects.
This configuration relies on Sensitive Data Protection (Cloud DLP) to find key files, Web Security Scanner to audit usage, and IAM Conditions for key expiry.
The primary requirement was discovering leaked private key files stored in public Cloud Storage buckets or scanning custom App Engine web applications for application-layer vulnerabilities.
This configuration attempts to use VPC Flow Logs, Network Analyzer / Cloud SQL insights, and Data Access audit logs on Cloud Storage to audit service account keys.
CreateServiceAccountKey) is an IAM control-plane administrative operation captured by default in Admin Activity audit logs, not Cloud Storage Data Access logs.The scenario required monitoring network traffic volume between Compute Engine instances and specific internal IP addresses or verifying firewall rule efficacy.
This configuration attempts to use Network Analyzer, Firewall Rules Logging, and Security Command Center (SCC) to manage and audit service account keys.
constraints/iam.disableServiceAccountKeyCreation, rather than reactive Cloud Functions triggered by SCC.The goal was to diagnose subnet IP exhaustion across Shared VPC service projects and verify that perimeter firewalls were blocking unauthorized egress network connections.
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