← GCDL·Google Cloud

Question 145 of 507

Scaling with Google Cloud operations →easyMultiple ChoiceObjective-mapped

Quick Answer

The answer is Cloud Asset Inventory, which provides the most efficient way to query VM inventory across projects because it offers a single, unified API to search resources across an entire organization. Instead of manually accessing each project individually, you can run one `gcloud asset search-all-resources` command with the `--asset-types=compute.googleapis.com/Instance` filter to retrieve all VM instances, their regions, machine types, and network configurations—including public IP addresses—in a single operation. On the Google Cloud Digital Leader exam, this tests your understanding of centralized resource management versus project-by-project approaches; a common trap is assuming you need to iterate through each project or use separate Compute Engine APIs. The key insight is that Cloud Asset Inventory is designed for org-wide visibility, not just per-project queries. Memory tip: think of Cloud Asset Inventory as your "org-wide search engine" for cloud resources—one query, all projects, no project hopping.

Cloud Digital Leader Scaling with Google Cloud operations Practice Question

This GCDL practice question tests your understanding of scaling with google cloud operations. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 cloud team wants to understand their current Google Cloud resource inventory — specifically, which VMs are running in each region, their machine types, and whether they have public IP addresses. Which approach most efficiently provides this across all projects?

Question 1easymultiple choice

Full question →

A
Log into each Google Cloud project individually through the Console and manually record VM details in a spreadsheet
Why wrong: Manual per-project console review is extremely time-consuming and error-prone at scale. It doesn't scale beyond a handful of projects and produces a point-in-time snapshot that immediately becomes stale.
B
Use Cloud Asset Inventory to run a single org-wide query that returns all VM instances, their regions, machine types, and network configurations across all projects
Cloud Asset Inventory is purpose-built for this. A single asset search for 'compute.googleapis.com/Instance' resources across the entire organization returns the complete VM inventory with all attributes (region, machine type, IP configuration) in seconds.
C
Check the Cloud Billing reports, which list all resources that have incurred charges by resource type
Why wrong: Billing reports show cost data aggregated by resource type and service, not a detailed inventory with configuration attributes like machine type or public IP status.
D
Enable VPC flow logs in each project to capture VM network activity
Why wrong: VPC flow logs capture network traffic metadata (source/destination IPs, bytes, ports). They don't provide a resource inventory of VM configurations.

Full breakdown with real-world context →

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

✓

Use Cloud Asset Inventory to run a single org-wide query that returns all VM instances, their regions, machine types, and network configurations across all projects

Cloud Asset Inventory provides a single, unified API to query resources across all projects in an organization. By using the `gcloud asset search-all-resources` command with the `--asset-types=compute.googleapis.com/Instance` filter, you can retrieve all VM instances along with their regions, machine types, and network configurations (including public IP addresses) in one operation, without needing to access each project individually.

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.

✗
Log into each Google Cloud project individually through the Console and manually record VM details in a spreadsheet
Why it's wrong here
Manual per-project console review is extremely time-consuming and error-prone at scale. It doesn't scale beyond a handful of projects and produces a point-in-time snapshot that immediately becomes stale.
✓
Use Cloud Asset Inventory to run a single org-wide query that returns all VM instances, their regions, machine types, and network configurations across all projects
Why this is correct
Cloud Asset Inventory is purpose-built for this. A single asset search for 'compute.googleapis.com/Instance' resources across the entire organization returns the complete VM inventory with all attributes (region, machine type, IP configuration) in seconds.
Related concept
Read the scenario before looking for a memorised answer.
✗
Check the Cloud Billing reports, which list all resources that have incurred charges by resource type
Why it's wrong here
Billing reports show cost data aggregated by resource type and service, not a detailed inventory with configuration attributes like machine type or public IP status.
✗
Enable VPC flow logs in each project to capture VM network activity
Why it's wrong here
VPC flow logs capture network traffic metadata (source/destination IPs, bytes, ports). They don't provide a resource inventory of VM configurations.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse Cloud Billing reports (cost-focused) or VPC flow logs (traffic-focused) with inventory tools, or assume manual per-project inspection is acceptable, when Cloud Asset Inventory is the only option designed for cross-project resource discovery at scale.

Trap categories for this question

Command / output trap
Billing reports show cost data aggregated by resource type and service, not a detailed inventory with configuration attributes like machine type or public IP status.

Detailed technical explanation

How to think about this question

Cloud Asset Inventory uses a real-time snapshot of the Resource Manager hierarchy (organizations, folders, projects) and the Cloud Asset API to index all supported resource types, including Compute Engine instances. The `search-all-resources` method returns results in a structured JSON format that includes fields like `location` (region), `machineType`, and `networkInterfaces` (which contain `accessConfigs` for public IPs). This approach avoids the need to iterate over projects or use multiple API calls, and it supports historical asset views for change tracking.

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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

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.

Related GCDL practice-question pages

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

Why cloud technology is transforming business practice questions

Practise GCDL questions linked to Why cloud technology is transforming business.

Fundamental cloud concepts practice questions

Practise GCDL questions linked to Fundamental cloud concepts.

Google Cloud products, services, and solutions practice questions

Practise GCDL questions linked to Google Cloud products, services, and solutions.

Scaling with Google Cloud operations practice questions

Practise GCDL questions linked to Scaling with Google Cloud operations.

Trust and security with Google Cloud practice questions

Practise GCDL questions linked to Trust and security with Google Cloud.

GCDL fundamentals practice questions

Practise GCDL questions linked to GCDL fundamentals.

GCDL scenario practice questions

Practise GCDL questions linked to GCDL scenario.

GCDL troubleshooting practice questions

Practise GCDL questions linked to GCDL troubleshooting.

Practice this exam

Start a free GCDL practice session

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

10 questions 20 questions 30 questions 50 questions Timed 30

GCDL practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this GCDL question test?

Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use Cloud Asset Inventory to run a single org-wide query that returns all VM instances, their regions, machine types, and network configurations across all projects — Cloud Asset Inventory provides a single, unified API to query resources across all projects in an organization. By using the `gcloud asset search-all-resources` command with the `--asset-types=compute.googleapis.com/Instance` filter, you can retrieve all VM instances along with their regions, machine types, and network configurations (including public IP addresses) in one operation, without needing to access each project individually.

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

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

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…

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.