Google-Workspace-Administrator 無料問題集「Google Cloud Certified - Professional Google Workspace Administrator」

（A）Develop a cadence of regular roadmap and business reviews with your partner.

（B）Put half of your organization on the Rapid Release Schedule to highlight differences.

（C）Regularly scan the admin console and keep track of any new features you identify.

（D）Create a Feature Release alert in the Alert Center to be alerted to new functionality.

（A）Enable single sign-on (SSO) with third-party identity providers and exclude the users who are using a different provider.

（B）Enable single sign-on (SSO) with Cloud Identity, and use Cloud Directory Sync to manage multiple identity providers.

（C）Nothing. Google uses cookies to establish a user's relationship to a device. This will cover multiple identity providers.

（D）Create Security Assertion Markup Language (SAML) based single sign-on (SSO) profiles and assign them to specific organizational units or groups of users.

（A）Disable Advanced Mobile Management and approve the device.

（B）Enable Advanced Mobile Management and unblock the device.

（C）Enable Advanced Mobile Management and approve the device.

（D）Disable Advanced Mobile Management and activate the device.

（A）Ask your network administrator to add the dedicated Meet IP address range for your users.

（B）View the Meet quality report of the employee.

（C）Restart the device of the employee.

（D）Check the Meet settings of the employee.

（A）You will need a Cloud SQL instance to store "G-Team' data.

（B）The Google Form will need to enforce Group naming conventions.

（C）The Apps Script will need to run on a timed interval to process new entries.

（D）The Apps Script will need to run as a Google Workspace admin.

（E）The Google Form will need to be limited to internal users only.

（A）Create a mail contact in the Google Workspace directory that has an email address of your- [email protected]

（B）Create a rule to forward mail in the [email protected] mailbox to your- [email protected]

（C）Create a recipient map in the Google Workspace Admin console that maps customercare@your- company.com to [email protected]

（D）Create a content compliance rule in the Google Workspace Admin console to change route to [email protected]

（A）Place the Field Technicians in a Group. Create and apply a domain wide 'Reject message' rule to the entire group.

（B）Disable automatic forwarding for all field technicians.

（C）Create a routing rule by using the Reject message option for the organization's domain, and apply the rule to the field technician organizational unit (OU).

（D）Place the field technicians in a separate organizational unit (OU) and disable the Gmail mobile app.

（A）From the Admin Console Billing Menu, turn off auto-assign, and then click into Assigned Users and export the data to Sheets.

（B）From the Google Workspace Reports Menu, run and download the Accounts Aggregate report, and export the data to Google Sheets.

（C）From the Admin Console Users Menu, download a list of all Users to Google Sheets, and join that with a list of ORGIDs pulled from the Reports API.

（D）From the Admin Console Users Menu, download a list of all user info columns and currently selected columns.

（A）Create a new Google Workspace domain with "mystartup.com," and create a trust between both domains for reusing the same security policies and sharing employee information within the companies.

（B）Create an alias domain, mystartup.com, in your existing Google Workspace domain, set up necessary DNS records, and create all startup employees with the alias domain as their primary email addresses.

（C）Create a secondary domain, mystartup.com, within your current Google Workspace domain, set up necessary DNS records, and create all startup employees with the secondary domain as their primary email addresses.

（D）Create the startup employees in the "mycompany.com' domain, and add a number at the end of the user name whenever there is a conflict. In Gmail > Routing, define a specific route for the OU that targets the startup employees, which will modify the email address domain to
"mystartup.com," and remove any numbers previously added. In addition, confirm that the SPF and DKIM records are properly set.

（A）Capture the Gmail labels used by the reported user.

（B）Capture the number of times the Event is set for recurrence to ensure that the host is not hitting the email limits.

（C）Capture the laptop OS version of the user to troubleshoot if there are older versions of the event being displayed.

（D）Capture the relevant Event IDs and the ICS files by using the Show original option.

（A）Create a custom query in BigQuery showing all suspicious login details.

（B）Use the login audit report to export all suspicious login details for analysis.

（C）Use the account activity report to export all suspicious login details for analysis.

（D）Create a custom dashboard with the security investigation tool showing suspicious logins.

（A）G Suite support articles

（B）Google Workspace Release Calendar

（C）Google Workspace Updates Blog

（D）Google Workspace Feature Ideas

（A）Change ownership of the Drive data to the user's Manager, then delete the user.

（B）Export the user's Drive data from Vault, then delete the user.

（C）Suspend the user until the end of the three-year period.

（D）Assign an Archive User (AU) license to the user.

（A）Force encryption on all inbound and outbound emails from your Workspace domain.

（B）Enforce confidential mode for all messages sent and received from your Workspace domain.

（C）Configure spoofing and authentication controls to quarantine messages that are perceived as threats.

（D）Train end users to mark messages as spam when they see something suspicious.

（E）Configure spoofing and authentication controls to warn end users about messages that are perceived as threats.

（A）Add the product's IP addresses as an approved sender.

（B）Allowlist the IP addresses of the third-party filtering product.

（C）List the IP addresses of the product as an Inbound Gateway.

（D）Add the product's IP addresses to your organization's SPF record.