The answer is that the domain is not verified for the Google-managed certificate on the frontend. This is the most likely cause because Google-managed certificates require domain ownership verification via DNS TXT or CNAME records, or through a challenge file; without this verification, the certificate cannot be provisioned with the correct Subject Alternative Names (SANs), leading to a mismatch when clients connect to the domain. On the Google Professional Cloud Network Engineer exam, this tests your understanding of the SSL proxy load balancer’s separation of frontend and backend certificates—a common trap is assuming the backend’s self-managed certificate covers the frontend, but the frontend’s Google-managed certificate must match the client-facing domain. Remember the memory tip: “Frontend must be verified, backend is just backend”—the load balancer terminates SSL at the frontend, so the domain verification applies only there, not to the backend instance group.
PCNE Configuring network services Practice Question
This PCNE practice question tests your understanding of configuring network services. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
You are configuring an SSL Proxy load balancer for HTTPS traffic. The backend service points to an instance group with a self-managed certificate. The load balancer's frontend uses a Google-managed certificate. Clients receive SSL errors indicating certificate mismatch. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The domain is not verified for the Google-managed certificate on the frontend.
When a Google-managed certificate is used on the frontend of an SSL proxy load balancer, the domain must be verified via DNS or a challenge file. If the domain is not verified, the certificate cannot be provisioned or validated, causing a mismatch between the certificate's Subject Alternative Names (SANs) and the domain clients are connecting to, resulting in SSL errors.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The SSL policy is configured to require TLS 1.3 only.
Why it's wrong here
TLS version mismatch would cause handshake failure, not certificate mismatch.
✓
The domain is not verified for the Google-managed certificate on the frontend.
Why this is correct
Google-managed certificates require domain verification; if not verified, the certificate may not issue, causing mismatch.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The backend self-managed certificate is not signed by a public CA.
Why it's wrong here
SSL Proxy does not validate backend certificate by default.
✗
The backend service must use a Google-managed certificate as well.
Why it's wrong here
Backend can use self-managed certificates.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between frontend and backend certificate validation, and candidates mistakenly think a backend certificate issue (like not being signed by a public CA) would cause frontend client errors, when in fact the frontend certificate mismatch is caused by domain verification failure for the Google-managed certificate.
Detailed technical explanation
How to think about this question
Google-managed certificates rely on Certificate Authority (CA) automation via ACME protocol, requiring domain ownership verification through DNS TXT records or HTTP challenge files. If verification fails, the certificate is not issued, and the load balancer may serve a default or placeholder certificate that does not match the client's requested domain, triggering browser SSL warnings. This is distinct from backend certificate issues, which are handled by the backend service's SSL policy and do not affect the frontend handshake.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Configuring network services — This question tests Configuring network services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The domain is not verified for the Google-managed certificate on the frontend. — When a Google-managed certificate is used on the frontend of an SSL proxy load balancer, the domain must be verified via DNS or a challenge file. If the domain is not verified, the certificate cannot be provisioned or validated, causing a mismatch between the certificate's Subject Alternative Names (SANs) and the domain clients are connecting to, resulting in SSL errors.
What should I do if I get this PCNE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
This PCNE 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 PCNE exam.
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.
Sign in to join the discussion.