Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An enterprise is migrating its on-premises workloads to Google Cloud and plans to adopt a mix of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) solutions. The Chief Information Security Officer (CISO) wants to establish a governance baseline by identifying the foundational security and operational obligations that Google Cloud assumes across all service models:
Which set of responsibilities does Google Cloud always manage, regardless of the chosen cloud computing model?
Identity and Access Management (IAM) configuration and data classification represent the administrative and governance controls used to define who has access to which cloud resources and how sensitive business information is categorized and protected. While Google Cloud provides the underlying IAM framework and enforcement engine, defining the policies within that framework is a core customer obligation.
Under the shared responsibility model, the customer is always responsible for securing what they bring to the cloud. Even in a fully managed Software as a Service (SaaS) environment—where Google Cloud manages almost the entire technology stack—the customer always retains responsibility for data security, data classification, and access policies. Google Cloud cannot determine which employees in an enterprise require access to specific financial or healthcare records; only the customer has the business context to make those governance decisions.
The question asked which security responsibilities always remain with the customer across every cloud deployment model, including IaaS, PaaS, and SaaS.
A common misconception during cloud migration is assuming that moving to a high-level service model like SaaS offloads all security tasks to the provider. In reality, misconfigured user access controls and overly permissive IAM bindings are among the most common customer-side cloud security risks.
Operating system patching, application source code security, and container image verification are operational security tasks focused on protecting the guest software environment and workload artifacts deployed onto cloud infrastructure. These tasks ensure that custom software, guest kernels, and third-party libraries are free from known exploitable vulnerabilities.
These responsibilities are not universally managed by Google Cloud across all service models; instead, they sit in the middle layers of the shared responsibility model and shift depending on the chosen consumption model:
The question asked which operational responsibilities belong to the customer when deploying containerized applications and custom virtual machines in an IaaS environment.
While Google Cloud provides curated Container-Optimized OS images and optional features like automatic node upgrades in GKE to help reduce operational toil, securing proprietary application code and custom container dependencies remains a customer obligation.
Regulatory data residency, Organization Policy constraints, and Customer-Managed Encryption Keys (CMEK) are specialized governance and cryptographic configuration controls. They allow enterprises operating in regulated industries—such as finance, healthcare, or government—to tailor their cloud environment to meet strict regional laws and internal risk management mandates.
While Google Cloud builds the global regions, provides the Organization Policy Service, and integrates Cloud Key Management Service (Cloud KMS), deciding how and where to apply these controls is strictly the customer's responsibility. Google Cloud provides default encryption automatically, but if an organization chooses to use CMEK or Cloud External Key Manager (Cloud EKM), the customer assumes responsibility for managing and rotating those keys. Similarly, the customer is the expert on their own business and legal obligations, meaning they must determine which geographic regions their data must reside in to comply with regulations like GDPR or HIPAA.
The question asked how a customer fulfills their governance and compliance obligations when configuring Google Cloud to protect regulated workloads.
In the shared responsibility and shared fate framework, Google Cloud provides attested infrastructure, compliance certifications, and security blueprints, while the customer is responsible for translating their legal requirements into concrete cloud configurations.
In the cloud shared responsibility model, the cloud provider is always responsible for protecting the cloud itself. Regardless of whether an organization adopts Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS), Google Cloud retains complete operational and security ownership of the underlying physical infrastructure, hardware stack, storage media, and global network.
While management of operating systems, runtime environments, and application code shifts between the customer and Google Cloud depending on whether IaaS, PaaS, or SaaS is used, the physical facilities, core networking, and default cryptographic protections form the immutable base of the shared responsibility model that Google Cloud always manages.
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