GOOGLE-WORKSPACE-ADMINISTRATOR practice question 3 of 25

Your organization has just appointed a new CISO. They have signed up to receive admin alerts and just received an alert for a suspicious login…

Full set: 199 questions

Domain Business initiatives

Your organization has just appointed a new CISO. They have signed up to receive admin alerts and just received an alert for a suspicious login attempt. They are trying to determine how frequently suspicious login attempts occur within the organization. The CISO has asked you to provide details for each user account that has had a suspicious login attempt in the past year and the number of times it occurred for each account. What action should you take to meet these requirements?
Answer options
A: Use the login audit report to export all suspicious login details for analysis. Correct answer
B: Create a custom dashboard with the security investigation tool showing suspicious logins.
C: Use the account activity report to export all suspicious login details for analysis.
D: Create a custom query in BigQuery showing all suspicious login details.
Correct Answer:
A. Use the login audit report to export all suspicious login details for analysis.
Explanation

The Login audit log within the Google Workspace Admin console is the most direct tool for this request. It allows an administrator to view, filter, and export detailed records of user login events. You can specifically filter for the "Suspicious login" event type, set a custom date range up to one year (with an appropriate Google Workspace edition), and then export the results to a Google Sheet or CSV file. This exported file will contain the detailed information required for analysis, such as user, timestamp, and IP address, allowing the CISO to easily count the occurrences for each user.

Why Incorrect

B. Creating a custom dashboard is for high-level visualization and monitoring trends, not for providing a detailed, exportable list of every single event instance as requested by the CISO.
C. The account activity report provides a summary of user status (e.g., last login time, 2-Step Verification status) but does not contain a detailed log of individual suspicious login attempts.
D. While BigQuery can store and query this data, it requires a pre-existing and configured log export setup. The Login audit log is the native, built-in tool for this specific administrative task.

References

1. Google Workspace Admin Help, "Login audit log." This document details the functionality of the Login audit log. It states, "As an administrator, you can use the Login audit log to track user sign-ins to your domain... For example, you can see when a user signed in, and from what IP address." It also lists "Suspicious login" as a filterable event. The document notes data retention is 1 year for Enterprise editions.

2. Google Workspace Admin Help, "View user reports in the Admin console." This source describes the various user reports. The "Account Activity" section confirms it shows summary data like "Last login date" and "2-Step verification enrollment," not a detailed log of suspicious login events.

3. Google Workspace Admin Help, "About the security investigation tool." This page explains that the investigation tool is used to "identify, triage, and take action on security and privacy issues." While it uses log data, the action of creating a dashboard (Option B) is for visualization, not providing the raw, detailed data export requested.

4. Google Cloud, "Google Workspace audit logs in BigQuery." This documentation outlines the process for exporting logs to BigQuery. It highlights that this is for "advanced analysis, and visualization," which confirms it's a more complex solution requiring prior setup, making the direct audit log (Option A) the more appropriate first step.

Scroll to Top