Before we start: what this course is and isn't
The Professional Cloud Network Engineer exam is built from one document: Google's exam guide. The current version is dated April 2026 (the file name starts with 042426). It is Google's own document. You can download it free from the certification page, and this course does not reproduce it. Keep your own copy open while you study and tick items off as we go.
This course is independent of Google and not endorsed by it. It is built to cover every item in the guide, but no course can promise you'll pass. That depends on your practice, your hands-on time and the exam on the day.
The guide describes the role like this: a Professional Cloud Network Engineer is "responsible for the design, implementation, and management of Google Cloud network infrastructure." The rest of the guide breaks that down into specific skills, such as VPC design, routing, load balancing, Cloud NAT, Cloud DNS, Cloud Interconnect and Cloud VPN, Network Intelligence Center, Cloud NGFW, Secure Web Proxy, VPC Service Controls and Google Cloud Armor.
Step 1: Get your facts from the official page
The first habit to build is to check the source yourself. Blog posts and forum threads repeat exam figures that were correct two versions ago. Go to the certification page (cloud.google.com/learn/certification/cloud-network-engineer) and confirm these details:
What to check on the official exam page What it said when this course was written
---------------------------------------- ------------------------------------------
Length 2 hours
Format 50-60 multiple choice and multiple select
Registration fee $200 (plus tax where applicable)
Languages English, Japanese
Delivery Online-proctored, or onsite at a test centre
Prerequisites None (3+ yrs industry, 1+ yr Google Cloud recommended)
Also linked Exam guide PDF, sample questions, training path
Gotcha: treat the right-hand column as a snapshot, not a promise. Prices, languages and question counts change. The official page is the only figure that counts on the day you book.
Try the official sample questions early. They aren't scored and they don't predict your result, but they show you exactly how the questions are worded.
Step 2: Know the six sections and their weights
The guide splits the exam into six sections, each with an approximate weight:
| # | Section (guide wording) | Weight |
|---|---|---|
| 1 | Designing and planning a Google Cloud VPC network | ~21% |
| 2 | Implementing a VPC network | ~20% |
| 3 | Configuring managed network services | ~16% |
| 4 | Configuring and implementing hybrid and multicloud network interconnectivity | ~16% |
| 5 | Managing, monitoring, and troubleshooting network operations | ~14% |
| 6 | Configuring, implementing, and managing a cloud network security solution | ~13% |
The weights add up to 100%. Sections 1 and 2 together make up about 41% of the exam, so VPC design and implementation is the core of the test. The rest is spread fairly evenly.
Use the weights to plan your study time. This short script splits a 60-hour study budget across the sections:
budget_hours = 60 # set this to your real budget
weights = {
"1 Design & plan VPC": 0.21,
"2 Implement VPC": 0.20,
"3 Managed services": 0.16,
"4 Hybrid & multicloud": 0.16,
"5 Operations": 0.14,
"6 Security": 0.13,
}
for section, w in weights.items():
print(f"{section:<24}{budget_hours * w:5.1f} h")
1 Design & plan VPC 12.6 h
2 Implement VPC 12.0 h
3 Managed services 9.6 h
4 Hybrid & multicloud 9.6 h
5 Operations 8.4 h
6 Security 7.8 h
Trade-off: the weights are a starting point. If you've run Interconnect for years but never touched VPC Service Controls, move hours from Section 4 to Section 6. Spend your time on your weak spots, scaled by how much each section counts.
Step 3: How this course maps to the guide
The course has 58 levels and follows the guide's order, Section 1 through Section 6. Each level covers named items from the guide, and the guide's own product names are used throughout because the exam uses them too. Every level ends with a short "what the exam asks about this" note. Where this course's summary and the guide differ, the guide wins.
Step 4: A method for "best answer" scenario questions
Most questions describe a company, a situation and a goal. Often two or three options would technically work. Only one fits every stated requirement. The deciding requirement is usually one of these five constraints:
- Cost: "most cost-effective", "minimise spend"
- SLA / availability: "99.99%", "no single point of failure"
- Security / compliance: "no internet access", "must not leave Google's network"
- Latency / performance: "lowest latency", "high throughput"
- Operations effort: "fewest steps", "managed service", "minimal maintenance"
The method:
- Read the last sentence first, which is usually the actual question.
- Underline the binding constraint, meaning the requirement that can't be traded away.
- Rule out each option that breaks it, and say why to yourself.
- Pick between the survivors using the secondary constraint, usually operations effort or cost.
Worked example
Compute Engine VMs in a subnet have only internal IP addresses. Security policy forbids any route to the internet. The VMs must read objects from Cloud Storage. What should you do?
- Binding constraint: security, meaning no internet path.
- Assign external IPs to the VMs: breaks the security constraint. Rule it out.
- Build a self-managed proxy VM with an external IP: breaks the security constraint and adds operations work. Rule it out.
- Create a Cloud VPN tunnel to on-premises: doesn't address the requirement at all. A distractor that just names a networking product.
- Enable Private Google Access on the subnet: lets VMs with only internal IPs reach Google APIs. This one survives.
# Enable Private Google Access on an existing subnet
gcloud compute networks subnets update app-subnet \
--region=europe-west2 \
--enable-private-ip-google-access
Distractors are rarely nonsense. They're real products used in the wrong situation. Ask yourself which constraint each one breaks, not just whether it works.
Best practice: watch for multiple-select questions. They tell you how many answers to choose, so read the wording carefully.
What the exam asks about this
Nothing in this level is scored. The exam tests networking, not how the exam is run. But the method from Step 4 applies to almost every question, and the section weights tell you where most of the marks are.
Key takeaways
- The exam guide (April 2026) is Google's free document. Download it from the certification page and use it as your checklist.
- Always check length, price, languages and delivery options on the official exam page, not second-hand.
- Six sections: ~21%, ~20%, ~16%, ~16%, ~14%, ~13%. VPC design and implementation together make up about 41%.
- Split your study hours by weight, then adjust for your weak spots.
- For scenario questions: find the binding constraint (cost, SLA, security, latency, ops effort), rule out options that break it, then decide between the survivors.
- This course is independent of Google, not endorsed by it, and cannot guarantee a pass.