Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is deploying a financial analytics platform on Google Cloud using Compute Engine virtual machines and Cloud Storage. The organization is preparing for an independent SOC 2 Type II compliance audit and needs to distinguish between security controls provided directly by Google Cloud versus controls that the enterprise's cloud architects must configure and operate.
According to the shared responsibility model, which security control is fully managed by Google Cloud and verified via Google's third-party audit reports?
In cloud computing's shared responsibility model, the cloud service provider (Google Cloud) is entirely responsible for the security of the cloud. This encompasses the physical data centers, underlying hardware provenance, server boards, custom security chips (such as Titan), and low-level hypervisor systems that host multi-tenant cloud services.
For compliance audits like SOC 2 Type II, ISO/IEC 27001, or PCI DSS, customers do not have direct physical access to Google data centers to perform inspections themselves. Instead, Google engages independent third-party auditors who evaluate these physical and foundational hardware controls annually:
Physical data center security and hardware cryptographic verification are strictly the domain of the cloud provider. Cloud architects cannot install physical barriers or modify Google's server firmware, making this an inherited control fully satisfied through Google's compliance documentation.
Identity and Access Management (IAM) and resource-level access control lists define which principals (users, service accounts, or groups) are permitted to perform specific operations on Google Cloud resources, such as Cloud Storage buckets and BigQuery datasets.
While Google provides the IAM platform and enforces authentication checks, the configuration and governance of access policies are entirely the responsibility of the customer:
The requirement was about the physical access controls to the servers executing the IAM authentication service, rather than the customer's assignment of access permissions.
Data classification, lifecycle/retention rules, and application-level logging involve identifying sensitive information, configuring storage bucket retention policies, and capturing transactional software logs to support auditing and business resumption.
Google provides the building blocks (such as Cloud Storage Object Retention Lock, Cloud Logging, and Sensitive Data Protection), but the configuration and execution of these controls belong to the customer:
The question asked about the physical destruction and sanitization of retired storage media handled by Google personnel in data center facilities.
Guest operating system patch management involves updating system kernels, patching software packages, and maintaining hardening configurations on Compute Engine virtual machines (an Infrastructure as a Service, or IaaS, offering).
Under the shared responsibility model for IaaS:
The workload was hosted entirely on a fully managed Serverless or PaaS platform (such as Cloud Run or App Engine standard environment), where Google manages the underlying container runtime and OS patches.
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