71-84

Your company is using Google Workspace Enterprise Standard. They have 200 meeting rooms defined for the main building and used daily by the 12,000 employees. Users are complaining they have difficulties finding a room available when searching within Google Calendar, even if several rooms are available (no one attending meetings in these rooms at that time). You have been asked to find a solution while minimizing the operational effort and avoiding any new expenses due to budget constraints. What should you do?

• Implement a third-party solution that will detect presence in the room and release it if nobody appears after a few minutes.

• Create a Google App Script that will inspect each room calendar for the next 12 hours, check attendees status, and send the room administrator an alert email for releasing the room if all attendees have declined but the room has not.

• Set the option "Allow calendar-based room release" for all targeted rooms.

• Upgrade to Google Workspace Enterprise Plus edition to benefit from additional features for automated machine learning (ML) based resources management.

Your company has just acquired a new group of users. They have been provisioned into the Google Workspace environment with your primary domain as their primary email address. These new users still need to receive emails from their previous domain. What is the best way to achieve this for these new users, without updating the information of preexisting users?

• Add the acquired domain as an alias to the primary Google Workspace domain.

• Add the acquired domain as a secondary domain to the primary Google Workspace domain, and then update the email information of all new users with alias emails.

• Update the Google-provided test domain to be the domain of the acquired company, and then update the email information of all new users with alias emails.

• Without adding a domain, update each user's email information with the previous domain.

The application development team requests 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 an approved allowlist, per security policy. You need to grant access for this app. What should you do?

• Enable all API access for Google Drive.

• Enable the "trust domain owned apps" setting.

• . Add OAuth Client ID to the Google Drive Trusted List.

• Allowlist the app in the Google Workspace Marketplace.

An administrator accidentally deleted several Workspace user accounts from the Google Admin Console two weeks ago. How can you recover the deleted user accounts?

• Open a Google support ticket, and request a recovery of all recently deleted users.

• Sign in to the Ad min console as Help Desk Admin, open user management, filter for "recently deleted," and recover.

• Sign in to the Admin console as Super Admin, open user management, filter for "recently deleted," and recover.

• Create a matter, go to legal hold, and create a legal hold for the user accounts.

You need to protect your users from untrusted senders sending encrypted attachments via email. You must ensure that these messages are not delivered to users' mailboxes. What step should be taken?

• Use the security center to remove the messages from users' mailboxes

• Use Google Vault to remove these messages from users' mailboxes.

• Enable a safety rule to send these types of messages to spam.

• Enable a safety rule to send these types of messages to a quarantine.

Your organization uses a third-party product to filter mail before it arrives at your Workspace Domain. How should you configure Gmail to ensure that inbound messages are not seen as a spam attack due to the volume of mail being received from this product?

• Add the product's IP addresses as an approved sender.

• Allowlist the IP addresses of the third-party filtering product

• Add the product's IP addresses to your organization's SPF record.

• List the IP addresses of the product as an Inbound Gateway.

Your organization is in the process of deploying Google Drive for desktop so that your users can access Drive files directly from their desktops. For security reasons, you want to restrict Drive for desktop to only company-owned devices. What two steps should you take from the admin panel to restrict Drive for desktop to only company-owned devices? (Choose two.)

• Create a company-owned device inventory using an asset tag.

• Devices > Endpoints > Add a filter > Management Type > Drive for desktop > Apply

• Apps > Google Workspace > Drive and Docs > Features and Applications > Google Drive for Desktop > Only Allow Google Drive for desktop on authorized devices

• Install the Google Endpoint Verification extension on machines using Drive for Desktop.

• Create a company-owned device inventory using serial numbers of devices.

The human resources (HR) team needs a centralized place to share key documents with the entire organization while protecting confidential documents and mitigating the risk of losing documents when someone leaves. These documents must be editable by the HR team members. What is the best way to set this up?

• Have the HR lead create a folder in their MyDrive for the non-confidential files, give edit access to the HR team, and give view access to the organization.

• Create a shared drive for the non-confidential files, give the HR team manager access, and give contributor access to the entire organization.

• Create a shared drive for non-confidential files, give the HR team content manager access, and give view access to the organization.

• Create a shared drive for all files, give the HR team content manager access, and give view access to the organization.

Your organization implemented Single Sign-On (SSO) for the multiple cloud-based services it uses. During authentication, one service indicates that access to the SSO provider is not possible due to invalid information. What should you do?

• Update the validation certificate.

• Verify that the Audience element in the SAML Response matches the assertion consumer service (ACS) URL.

• Run nslookup to confirm that the service exists.

• Ensure that Microsoft's Active Directory Federation Services 2.0 sends encrypted SAML Responses in default configurations.

You have configured SSO using a third-party IDP with your Google Workspace domain. An end user has reported that they cannot sign in to Google Workspace after their username was changed in the third-party SSO product. They can sign in to their other internal applications that use SSO, and no other users are experiencing issues signing in. What could be causing the sign-in issue?

• The SAML assertion provided by the third-party IDP is presenting a username that conflicts with the current username configured in Google Workspace.

• The user's Google password was changed administratively, which is causing a sign-in failure.

• The issued certificate for that user has been revoked and must be updated before the user can have another successful sign in.

• The SAML assertion is providing the user's previous password attached to their old username.