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.
A financial enterprise is preparing for an annual multi-framework compliance audit (including ISO/IEC 27001, SOC 2 Type II, and PCI DSS) for a cloud-native transaction processing application hosted on Google Cloud.
The external compliance auditor mandates two distinct verification streams:
Which strategy correctly satisfies these requirements under the Google Cloud shared responsibility model?
This approach attempts to enforce customer compliance by organizing on-premises physical audits of multi-tenant cloud datacenters, turning off administrative visibility logging, and treating penetration testing as a gated activity requiring cloud provider pre-authorization.
The customer were managing a dedicated private on-premises datacenter where physical access is directly controlled and all external security evaluations require advance internal operational sign-offs.
This option relies solely on contract documentation (such as the Cloud Data Processing Addendum) and public service health dashboards to satisfy audit controls around data security and access tracking.
The audit requirement was strictly limited to establishing commercial contractual terms and verifying historical high-level platform SLA availability.
Under the Google Cloud shared responsibility model, compliance assurance is divided between the cloud service provider (security of the cloud) and the customer (security in the cloud). Customers validate Google's underlying physical infrastructure, datacenter operations, hardware root of trust, and hypervisor controls by reviewing independent third-party audit attestations—including SOC 1/2/3 reports, ISO/IEC 27001/27017/27018 certifications, and PCI Attestation of Compliance (AOC) available through the Compliance Reports Manager or Google Cloud representative.
This approach cleanly fulfills regulatory boundaries by relying on verified external attestations for vendor-managed layers while actively architecting detective, preventive, and assessment controls across customer-managed assets.
This option mistakenly assumes that Google's public compliance attestations fully cover the guest operating system and application tiers, while attempting to use internal Google infrastructure systems for customer workload verification.
The workload was a fully turnkey Google-managed software service where the customer maintains zero configuration or deployment responsibility.
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