Free Google Cloud-Digital-Leader Actual Exam Questions - Question 8 Discussion
application is distributed across multiple containers.
Which Google Cloud product should the organization use?
Why not Cloud Logging (D)? It collects logs from containers, so if the issue shows up in runtime logs, searching there might help find the problem. Direct source search isn’t always possible.
Makes sense that only Cloud Console (A) lets you directly search source code across containers.
A. Cloud Console lets you access Cloud Source Repositories directly, so it’s the only option that actually lets you search source code across containers. The others are for monitoring or logs, not code itself.
Since the app runs in containers, the source might be in Cloud Source Repositories, which you access via Cloud Console. The other options focus on runtime data, not code itself. Could the question imply looking for code errors rather than runtime issues?
D doesn’t seem right since Cloud Logging is more about viewing logs, not searching source code directly. B and C focus on performance data and monitoring, not code analysis. So even if the question doesn’t specify storage, options other than A don’t really help with searching the actual source across containers. If the code’s stored somewhere accessible through Console, that would be the logical choice.
It’s A because Cloud Console lets you browse source code if it’s in Cloud Source Repositories, which is common for containerized apps. The question hints at source code access, so that fits better than just logs.
I’m thinking B and C can be ruled out since they focus on performance and metrics, not code search. A and D are the main contenders, but does the Console really let you search inside all containers’ source code directly?
It’s D since logs might include code snippets or error traces across containers.
It’s A. The Console lets you access Cloud Source Repositories and other integrated tools where you can manage and search source code. The other options, like Cloud Logging or Trace, focus more on runtime data, not the actual code. So if you need to look through the source spread across containers, the Console is your best bet to tie everything together and find what you need.
A/D? Neither Cloud Logging nor the Console really focuses on searching code directly. Cloud Trace and Monitoring track performance and metrics, so they’re out. The Console might let you browse resources but not do deep code searches across containers. Honestly, Google Cloud doesn’t have a built-in product specifically for searching source code inside containers. You’d probably need to pull the code out and scan it with other tools or set up something custom. If forced to pick from these, maybe A makes the most sense since it’s the general interface, but it’s a stretch.
Doesn’t Cloud Logging keep track of logs which might help find issues? I’d go with D.