Question 51 of 500
Integrating Google Cloud serviceshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is Cloud Service Mesh (Anthos Service Mesh) because it is the only Google Cloud service that natively combines mutual TLS encryption with fine-grained authorization policies based on service identity. For service-to-service authentication, authorization, and encryption in a microservices environment, Cloud Service Mesh automatically provisions and rotates certificates for each workload, enabling encrypted mTLS communication and allowing you to define access rules using the requesting service’s identity rather than IP addresses or API keys. On the Google Professional Cloud Developer exam, this question tests your understanding of how service mesh decouples security from application code, and a common trap is confusing it with Cloud Endpoints (which handles API management for external clients) or Cloud Armor (which is for DDoS protection). Remember the key distinction: if the requirement involves enforcing policies between internal microservices using identity-based access, think “mesh.” A helpful mnemonic is “MESH = Mutual TLS, Encryption, Service identity, Hierarchical policies.”

PCD Integrating Google Cloud services Practice Question

This PCD practice question tests your understanding of integrating google cloud services. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company is migrating a monolithic application to microservices on Google Cloud. They have strict requirements for service-to-service communication: requests must be authenticated, authorized, and encrypted in transit. They also need to enforce fine-grained access control based on the requesting service identity. Which Google Cloud service should they use to achieve these goals?

Question 1hardmultiple choice
Full question →

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

Cloud Service Mesh (Anthos Service Mesh)

Option C is correct because Cloud Service Mesh (Anthos Service Mesh) provides mutual TLS, fine-grained authorization policies, and service identity. Option A is for API management, option B is for DDoS protection, and option D is for serverless ingress control.

Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cloud Run with ingress control

    Why it's wrong here

    Cloud Run ingress control is limited to external access, not fine-grained service-to-service.

  • Cloud Armor with IAM

    Why it's wrong here

    Cloud Armor is for DDoS protection, not for service-to-service authentication.

  • Cloud Service Mesh (Anthos Service Mesh)

    Why this is correct

    Cloud Service Mesh provides mutual TLS and policy-based access control for microservices.

    Related concept

    Authentication checks who the user is.

  • Cloud Endpoints with API keys

    Why it's wrong here

    Cloud Endpoints is for API management, not for service-mesh level security.

Common exam traps

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Detailed technical explanation

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Key takeaway

Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCD questions on access control and AAA configuration.

Related practice questions

Related PCD practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCD practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PCD question test?

Integrating Google Cloud services — This question tests Integrating Google Cloud services — Authentication checks who the user is..

What is the correct answer to this question?

The correct answer is: Cloud Service Mesh (Anthos Service Mesh) — Option C is correct because Cloud Service Mesh (Anthos Service Mesh) provides mutual TLS, fine-grained authorization policies, and service identity. Option A is for API management, option B is for DDoS protection, and option D is for serverless ingress control.

What should I do if I get this PCD question wrong?

Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PCD questions on access control and AAA configuration.

What is the key concept behind this question?

Authentication checks who the user is.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This PCD 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 PCD exam.