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.
A global retail organization is migrating its IT infrastructure from a traditional on-premises data center to Google Cloud. In their legacy on-premises environment, the security architecture relied on the following practices:
How should the organization adapt its security strategy to align with Google Cloud's security model?
Modern cloud security operates on a Zero Trust philosophy combined with software-defined infrastructure. Rather than relying on physical network boundaries (often called "castle-and-moat" security) and dedicated hardware appliances, Google Cloud uses software-defined controls—such as Identity and Access Management (IAM), Virtual Private Cloud (VPC) firewall rules, VPC Service Controls, and Google Cloud Armor—to secure resources dynamically across a global infrastructure.

Traditional physical perimeters cannot effectively protect a globally distributed workforce accessing cloud applications from anywhere. By adopting software-defined, identity-centric controls, the organization achieves consistent, automated security that scales seamlessly across Google Cloud's global network while preventing lateral movement if a single credential is compromised.
Traffic backhauling (or hair-pinning) is a legacy networking practice where an organization forces all remote and cloud-bound network traffic to travel back to a centralized, on-premises data center for inspection by physical hardware appliances before forwarding it to cloud services.
The organization needed to inspect traffic exclusively destined for legacy servers that remain hosted inside their private on-premises data center rather than modernizing their security strategy for workloads migrated to Google Cloud.
Instead of backhauling traffic to physical hardware, organizations on Google Cloud use Google Cloud Armor and Google Front End (GFE) servers to detect and stop malicious requests and DDoS attacks right at the global network edge.
Physical data center security encompasses the layered physical safeguards that Google deploys at its global facilities to protect server hardware and storage media. These controls include perimeter fencing, vehicle access barriers, metal detectors, biometrics, laser beam intrusion detection, and 24/7 monitoring by high-resolution cameras and security guards.
The question asked how Google Cloud fulfills its responsibility under the Shared Responsibility Model to prevent unauthorized physical tampering or theft of the underlying servers hosting customer workloads.
While Google handles physical security, hardware hardening, and custom Titan security chips at the infrastructure layer, customers must still implement logical, software-defined controls—such as Cloud Identity, MFA, and least-privilege IAM roles—to govern who can access their cloud applications and data.
Physical firewall appliances are dedicated, rack-mounted hardware devices traditionally installed at the edge of an on-premises data center to inspect network packets, enforce access control lists, and separate trusted internal networks from untrusted external networks.
The organization was migrating its servers to a traditional colocation facility (where customers rent physical rack space and provide their own servers, switches, and hardware firewalls) rather than adopting a public cloud platform.
In Google Cloud, traditional hardware appliances are replaced by globally scalable, software-defined services. Organizations enforce network segregation and perimeter security using VPC firewall rules, Shared VPC, VPC Service Controls, and Google Cloud Armor, all of which can be provisioned consistently using Infrastructure as Code (IaC).
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