Google-Workspace-Administrator Exam Dumps - Google Cloud Certified - Professional Google Workspace Administrator

Access Google Vault: The Vault admin should log in to Google Vault.

Create a New Matter: In Google Vault, create a new matter specifically for this investigation related to the disgruntled employee.

Place Data on Hold: Place all the user’s email and Drive data on hold to ensure it is preserved. This prevents the data from being permanently deleted or altered.

Search for Data: Use Google Vault’s search functionality to locate relevant emails and documents that may pertain to the leak.

Export Data if Needed: If necessary, export the preserved data for further analysis and review by the security team.

Collaborate with Security Team: Share the findings with the security team to aid in their investigation of the data leak.

References:

Google Vault Help - Create and Manage Matters

Google Vault Help - Place Data on Hold

Apps > add SAML apps to your domain:

When switching to Google as the Identity Provider (IDP) for Single Sign-On (SSO), you need to configure Google Workspace to act as the SSO provider for third-party applications. This involves adding the necessary SAML (Security Assertion Markup Language) applications to your domain within Google Workspace.

Navigate to the Admin console, go to Apps > Web and mobile apps, and add SAML apps to your domain. This allows Google to authenticate users for those apps.

Disable SSO with third party IDP:

Since you are switching from an external SSO provider to Google Workspace as your IDP, you must disable the current SSO configuration with the third-party provider.

Go to the Admin console, navigate to Security > Set up single sign-on (SSO) with a third party IdP, and disable the existing SSO setup. This ensures that users will now authenticate directly through Google Workspace instead of the previous SSO provider.

References:

Google Workspace Admin Help: Set up your own custom SAML app

Google Workspace Admin Help: Disable SSO with third party IdP

To investigate and fix the issue where the new hardware does not show the expected calendar events, follow these steps:

Sign in to the Google Admin console: Use an account with super administrator privileges.

Verify the resource calendar:

Go to Apps > Google Workspace > Calendar > Resources.

Ensure that the conference room resource calendar has been created.

Associate the Meet hardware:

Go to Devices > Google Meet hardware.

Find the new hardware device and check its settings.

Ensure the device is associated with the correct conference room resource calendar.

Check calendar permissions:

Go to Calendar > Manage resources.

Ensure the calendar associated with the Meet hardware has the appropriate access permissions set to "See all event details."

References:

Google Workspace Admin Help - Manage resources

Google Workspace Admin Help - Google Meet hardware

Open Developer Tools:

In Chrome, click the three dots menu (More).

Select "More Tools" > "Developer Tools".

Replicate the Error:

Go to the "Network" tab in Developer Tools.

Reload the Gmail page to replicate the 500 error.

Export HAR:

After the error is replicated, right-click on the network log.

Select "Save all as HAR with content".

Save the HAR file, which contains detailed logs of the network activity.

This file can then be provided to Google support for further analysis.

References

Google Workspace Admin Help: Troubleshooting Network Issues

Access Admin Console: Log in to the Google Admin console.

Navigate to Security Settings: Go to Security > Sandbox.

Configure Security Sandbox: Enable the security sandbox feature and apply it to the sales team’s organizational unit.

Policy Setup: Configure policies to ensure that email attachments received by the sales team are automatically analyzed in the security sandbox.

Monitor and Review: Regularly monitor the sandbox reports and adjust the settings as needed to maintain protection without disrupting business operations.

References:

Google Workspace Admin Help - Security Sandbox

Google Workspace Admin Help - Advanced Phishing and Malware Protection

https://support.google.com/a/answer/172177

Access the Admin Console: Sign in to your Google Admin console.

Navigate to Security Settings: Click on "Security" and then "API controls."

Manage Third-Party App Access: Click on "Manage third-party app access."

Check OAuth Scopes: Locate the CRM solution and ensure that it has the necessary OAuth scopes, particularly for Google Drive and Gmail.

Grant Access: If necessary, adjust the settings to grant the required scopes.

Verify Integration: Confirm that the CRM solution now has access to the necessary data and that employees can see contacts and documents.

References:

Google Workspace Admin Help: Manage third-party app access

Download Inventory Template:

Navigate to the Google Admin console.

Go to Devices > Company-owned inventory.

Click "Download CSV template" to get the template file.

Enter Device Information:

Open the CSV template file.

Enter the Device OS and serial number for each company-owned device.

Upload the CSV File:

Return to the Company-owned inventory section in the Admin console.

Click "Upload CSV" and select the completed template file.

Confirm and upload the file to update the inventory.

This process ensures that all company-owned devices are tracked accurately in the Google Workspace admin panel.

References

Google Workspace Admin Help: Add Company-owned Devices