Free Google Associate Cloud Engineer Actual Exam Questions - Question 1 Discussion

Actually, filtering by Configuration and Service Account (option A) is the way to go because service account creation is a config event, not data access. Options C and D deal with Data Access logs, which are more for actions on data rather than resource creation. Between A and B, B filters by Google Project, which is broader—service accounts are distinct resources, so you want to narrow it down specifically to Service Account. So yeah, option A makes the most sense here.

A/C? Creation should be under Configuration, but if Data Access logs are enabled for admin activities, it might show creation too. Still, A feels like the safer bet since it's a config change.

A vs B, A seems better since Resource type should be Service Account, not Google Project.

If it’s about when the account itself was created, filtering by Resource type Service Account seems more direct. Not sure if Data Access logs even capture creation events though, that feels more about actions on data, not config changes. Could B still make sense if it logs project-level changes?

Probably A. Creating a service account is a config change, so filtering by Configuration and Service Account makes the most sense to find its creation time.

A/B? Since creating a service account changes settings, it feels more like Configuration. Plus, filtering by Service Account resource type (option A) should pinpoint it better than Google Project (B).

Maybe C, since creating a service account might count as data access, not just config.

It’s A for me. Creation of a service account is definitely a configuration change, so filtering the Activity log by Configuration and Service Account makes the most sense. Data Access logs are more about reading or modifying data, not resource creation. Plus, filtering by Google Project in this case would pull in too many unrelated changes, making it harder to pinpoint the exact creation event.

A vs C? Creation feels like a config change, not data access.

I think we can rule out B since filtering by Google Project might include too many unrelated changes. C seems plausible if creation is considered a data access event, but not sure if service account creation falls under that category.

I’d rule out D since Data Access with Google Project seems too broad for a specific service account creation event. A feels more targeted by filtering Service Account under Configuration. So, A.

Maybe B makes sense here because the service account is tied to the Google Project, and filtering by project might capture all related creation events. Also, Configuration category tracks changes in settings and resource creation, so combining those filters could show the creation time more reliably than just filtering by Service Account alone. The Data Access category usually tracks read/write operations on data, which might not include resource creation details.

Option C since Data Access tracks API calls like creation, not just config changes.

Makes sense to focus on configuration since creation changes settings. Option A fits because it filters by service account and config category, which tracks creation activities precisely.

It’s A because creation is a config event, and filtering by Service Account is the most precise.

I think the best choice is A. Service account creation is definitely a configuration change, so focusing on the Configuration category is right. Also, filtering by Service Account as the resource type narrows it down exactly to those events. The Data Access category is more for API calls or data operations, so C and D don’t seem to fit here. B filters by Google Project, which feels too broad since we want to pinpoint service account creation specifically. So, A matches the criteria for checking creation time through the activity logs.

A makes sense because service account creation is a configuration change, so filtering by Configuration and Service Account should show that event. The other options focus on Data Access, which is more for read/write operations, not creation.

Maybe A, filtering the Activity log by Configuration and Service Account makes sense here.