Cloud Digital Leader Trust and security with Google Cloud Practice Question
A CISO is implementing a Zero Trust security architecture for the company's Google Cloud environment. Under Zero Trust, which fundamental assumption about network traffic changes compared to traditional perimeter-based security?
⚠ Common exam trap
Test-takers frequently confuse Zero Trust's 'never trust, always verify' with a blanket denial of all traffic (Option C), when in reality it requires explicit verification for each request, not static allowlisting.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Zero Trust assumes no traffic is trusted by default regardless of network origin — every request must be explicitly authenticated and authorized based on identity, device posture, and context
Zero Trust fundamentally shifts from implicit trust based on network location to explicit verification of every request. In Google Cloud, this means every API call, regardless of whether it originates from within the VPC or the internet, must be authenticated (e.g., using OAuth 2.0 or service account keys) and authorized based on identity, device posture, and context, as enforced by tools like Identity-Aware Proxy (IAP) and VPC Service Controls.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Zero Trust assumes that internal network traffic is more secure than external traffic because it has passed through the corporate firewall
Why it's wrong here
This describes the traditional perimeter-based model that Zero Trust explicitly dismantles. Assuming the corporate firewall creates a trusted inside is dangerous because attackers who breach one host can move laterally, and compromised devices or rogue employees already operate from inside the perimeter. Zero Trust treats every network—internal or external—as hostile and enforces per-request verification based on identity, device health, and context, not source IP or firewall traversal.
- ✓
Zero Trust assumes no traffic is trusted by default regardless of network origin — every request must be explicitly authenticated and authorized based on identity, device posture, and context
Why this is correct
This is the core Zero Trust principle: 'never trust, always verify.' A request from inside the VPC receives the same verification scrutiny as a request from the public internet. This model is more appropriate for cloud environments where the network perimeter no longer has clear meaning — employees, services, and attackers can all be inside the 'perimeter.'
- ✗
Zero Trust assumes all traffic is malicious and blocks all requests by default, requiring explicit allowlisting for each connection
Why it's wrong here
Zero Trust doesn't block all traffic — it requires all traffic to be verified. 'Never trust, always verify' means authentication and authorization for every request, not blocking everything. Legitimate users and services can access what they need once verified.
- ✗
Zero Trust eliminates the need for encryption since all traffic is assumed to be on secure internal networks
Why it's wrong here
Zero Trust actually mandates encryption rather than removing it. Since no network segment—including the corporate LAN or VPC—is considered inherently trustworthy, all traffic is presumed susceptible to eavesdropping and must be protected with TLS, IPSec, or similar mechanisms. Authentication and authorization verify the identity and posture of a request, but they do not protect the payload in transit; encryption ensures confidentiality and integrity regardless of network placement.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Service account
A service account is a special type of account used by an application or a virtual machine, rather than a human user, to authenticate and interact with cloud services and APIs securely.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
About these practice questions
This GCDL question is part of Courseiva's 829-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.