Free GOOGLE-WORKSPACE-ADMINISTRATOR Exam Braindumps
Professional Google Workspace Administrator Questions 46–50 (page: 11)

Updated On: 10-Feb-2026

Your company (your-company.com) just acquired a new business (new-company.com) that is running their email on-premises. It is close to their peak season, so any major changes need to be postponed. However, you need to ensure that the users at the new business can receive email addressed to them using your- company.com into their on-premises email server. You need to set up an email routing policy to accomplish this.

What steps should you take?

  1. Set up an Outbound Mail Gateway to route all outbound email to the on-premises server.
  2. Set up accounts for the new employees, and use mail forwarding rules to send to the on-premises server.
  3. Set up an Inbound Mail Gateway to reroute all inbound email to the on-premises server.
  4. Set up a Default route with split delivery to route email to the on-premises server.

Answer(s): D

Explanation:

Access the Admin Console:
Log in to the Google Workspace Admin console at https://admin.google.com/.
Configure Email Routing:
Navigate to "Apps" > "Google Workspace" > "Gmail" > "Default routing".
Set Up Split Delivery:
Create a new default routing rule.
Under "Add setting," click on "Routing."
In the "Add setting" box, under "Inbound," select "Configure" next to "Routing."

Under "Add setting," name your routing policy.
In the "Email messages to affect" section, specify the conditions for the rule (e.g., recipients in the new-company.com domain).
Route to On-Premises Server:
In the "Route" section, select "Modify message" > "Add more recipients." Enter the on-premises email server information (e.g., SMTP relay server) to forward emails to the on- premises server.
Save the rule and ensure it is active.
Test the Configuration:
Send test emails to ensure that emails are correctly routed to the on-premises server as per the split delivery setup.
Monitor the email flow and make adjustments if necessary to ensure smooth operation during the peak season.
Reference
Google Workspace Admin Help: Set up routing for your domain or organization Google Workspace Admin Help: Configure routing for mail in Google Workspace



A user does not follow their usual sign-in pattern and signs in from an unusual location.

What type of alert is triggered by this event?

  1. Suspicious mobile activity alert.
  2. Suspicious login activity alert.
  3. Leaked password alert.
  4. User sign-in alert.

Answer(s): B

Explanation:

Identify Suspicious Login Activity:
Google Workspace triggers a suspicious login activity alert when a user signs in from an unusual location or device that is not part of their regular sign-in pattern.
Review Alerts:
Go to the Google Workspace Admin console.
Navigate to "Security" > "Dashboard" > "Suspicious login activity". Review the details of the alert to determine the nature of the suspicious login.
Take Appropriate Actions:
Investigate the alert to ensure that the login attempt is legitimate. If the login is deemed suspicious, follow security protocols to secure the user account, such as resetting the password or enabling two-factor authentication.
Reference
Google Workspace Admin Help: Review security alerts



Your large organization, 80,000 users, has been on Google for two years. Your CTO wants to create an integrated team experience with Google Groups, Teams Drives, and Calendar. Users will use a Google Form and Apps Script to request a new "G-Team." A "G-Team' is composed of a Google Group and a Team Drive/ Secondary Calendar that is shared using that Google Group.

What two design decisions are required to implement this workflow securely? (Choose two.)

  1. The Apps Script will need to run as a Google Workspace admin.
  2. You will need a Cloud SQL instance to store "G-Team' data.
  3. The Google Form will need to be limited to internal users only.
  4. The Apps Script will need to run on a timed interval to process new entries.
  5. The Google Form will need to enforce Group naming conventions.

Answer(s): C

Explanation:

Subscribe to the Google Workspace Release Calendar:
Go to the Google Workspace Updates blog at https://workspaceupdates.googleblog.com/. Subscribe to the release calendar by clicking on the "Subscribe to updates" button. This will provide you with real-time updates about new features and changes in Google Workspace.
Join the Google Cloud Connect Community:
Visit the Google Cloud Connect Community at https://cloudconnectcommunity.google/. Join the community to engage with other Google Workspace administrators and users. Participate in discussions, ask questions, and stay informed about best practices and upcoming features.
Reference
Google Workspace Updates Blog
Google Cloud Connect Community



The application development team has come to you requesting that a new, internal, domain-owned Google Workspace app be allowed to access Google Drive APIs. You are currently restricting access to all APIs using approved whitelists, per security policy. You need to grant access for this app.

What should you do?

  1. Enable all API access for Google Drive.
  2. Enable "trust domain owned apps" setting.
  3. Add OAuth Client ID to Google Drive Trusted List.
  4. Whitelist the app in the Google Workspace Marketplace.

Answer(s): C

Explanation:

Navigate to the Google Admin console at admin.google.com. From the Admin console Home page, go to "Security" and then to "API controls." In the "API controls" section, click on "Manage Third-Party App Access." Here, you can add the OAuth Client ID of your internal app to the trusted list. This ensures that only apps you have vetted and approved can access Google Drive APIs, complying with your security policy.
Enter the OAuth Client ID of the new app and save the changes. This process ensures that the new, internal, domain-owned app can access Google Drive APIs without compromising the security policies in place.


Reference:

Google Workspace Admin Help - Manage API client access



Several customers have reported receiving fake collection notices from your company. The emails were received from accounts.receivable@yourcompany.com, which is the valid address used by your accounting department for such matters, but the email audit log does not show the emails in question. You need to stop these emails from being sent.

What two actions should you take? (Choose two.)

  1. Change the password for suspected compromised account accounts.receivable@yourcompany.com.
  2. Configure a Sender Policy Framework (SPF) record for your domain.
  3. Configure Domain Keys Identified Mail (DKIM) to authenticate email.
  4. Disable mail delegation for the accounts.receivable@yourcompany.com account.
  5. Disable "Allow users to automatically forward incoming email to another address."

Answer(s): A,B

Explanation:

Change the password for the suspected compromised account:
Sign in to the Google Admin console.
From the Admin console Home page, go to "Users."
Find and select the account "accounts.receivable@yourcompany.com." Click on "Security" and then "Password."
Follow the instructions to change the password.
Configure a Sender Policy Framework (SPF) record for your domain:

Log in to your domain host (e.g., GoDaddy, Bluehost). Locate the page for updating your domain's DNS records. Add a new TXT record for your domain with the SPF rule, typically something like:
v=spf1 include:_spf.google.com ~all
Save the changes to update the DNS records.
Changing the password helps secure the compromised account, while configuring SPF helps prevent email spoofing, ensuring that fake emails are less likely to be delivered as though they come from your legitimate email address.


Reference:

Google Workspace Admin Help - Change or reset a user's password Google Workspace Admin Help - Set up SPF records



Viewing page 11 of 41
Viewing questions 51 - 55 out of 199 questions


Post your Comments and Discuss Google GOOGLE-WORKSPACE-ADMINISTRATOR exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!