Free Google Associate Cloud Engineer Actual Exam Questions - Question 15 Discussion
You want to verify activities for a particular user for these buckets, using the fewest possible steps.
You need to verify the addition of metadata labels and which files have been viewed from those
buckets. What should you do?
Maybe B. Stackdriver logs are designed for detailed auditing, so filtering them should show both metadata label changes and file views without missing anything. Activity logs might be too high-level for this.
Good point about the depth of Stackdriver logs, but I’d also note that Activity logs in the Console might be quicker if you just want a simple check on metadata labels. Still, B seems more thorough for both tasks. B
B. Stackdriver logs capture detailed data access info including label edits and file reads, so filtering there covers both without switching views or consoles.
A/B? Activity log in the Console is usually high level and might miss detailed file reads, but it’s quick for metadata changes. Stackdriver logs (B) are more detailed and include data access logs, so they should have both label changes and file views. Creating a trace (D) seems overkill here, and just viewing the bucket (C) won’t show access history. Since the question wants the fewest steps, filtering Stackdriver logs directly seems like the best bet to cover both kinds of events at once.
Good point about data access logging. Only Stackdriver logs (B) can show detailed file views and metadata edits across multiple buckets in one place, so B feels like the best pick here.
It’s B because the Stackdriver log captures detailed data access events, including file views and metadata label changes, while the Activity log mainly covers admin-type actions. Since you want to track both label additions and file views specifically for a user, filtering Stackdriver logs is the most comprehensive and straightforward method across all buckets. The console’s Storage section (C) won’t show user activity, and creating a trace (D) is for performance, not auditing. So B makes sense for thorough verification with minimal hassle.
It’s A, since Activity log filters easily by user for both label edits and file views.
A. The Activity log is designed to give a quick, user-focused view of actions across services, including changes to metadata labels and file accesses. Since you want to verify this for a specific user and minimize steps, filtering the Activity log is probably the most straightforward way. Stackdriver logs (B) offer more detailed raw data but require extra filtering and parsing. Options C and D don’t really track user-specific activity in a simple way, so they seem less fitting here.
A/B? I get why B sounds right since Stackdriver (now Cloud Logging) has detailed logs, but the question wants the fewest steps. From my experience, the Activity log in GCP Console (A) lets you filter by user and see metadata changes plus file views pretty quickly without leaving the console or setting up extra filters. D is off since trace is for latency, and C won't show detailed access info. So it’s between A and B, but A seems simpler for a quick check.
Maybe A, since the Activity log in GCP Console can be filtered by user and shows metadata changes and file access without needing to dig into Stackdriver separately. Could be the quickest route.
This one feels like B to me. Stackdriver logs are where you get detailed info on who did what, including metadata changes and file views. The Activity log in the console (A) usually shows higher-level actions, but not all the nitty-gritty details you need here. So filtering Stackdriver logs would be the most straightforward way to verify specific user activities across those buckets.
B since Stackdriver logs detailed access info for storage activities.