リアルGoogle-Workspace-Administrator問題集でGoogle正確な解答2026年最新版を試そう [Q53-Q70]

Rate this post

リアルGoogle-Workspace-Administrator問題集でGoogle正確な解答2026年最新版を試そう

Workspace Administrator Google-Workspace-Administrator試験練習問題集

Google Cloud Certified -Professional Google Workspace Administrator Examは、Googleワークスペースの管理と管理に関する個人の知識とスキルを評価するように設計されています。この試験は、組織内のGoogleワークスペースの管理と展開を担当するIT専門家を対象としています。 Google Workspaceの機能、セキュリティ、および管理機能を深く理解する必要があります。この試験に合格して、Googleワークスペースを効果的に管理および管理する専門知識があることを示しています。これは、キャリアの進歩と雇用機会に役立つ可能性があります。

Google Workspaceは、あらゆる規模のビジネスや組織の生産性を大幅に向上させることができる、強力なクラウドベースの生産性ツールのスイートです。より多くの企業がGoogle Workspaceに頼ってワークフローとコラボレーションを効率化するにつれて、これらのツールを管理することができる資格を持つ資格者の需要はますます重要になっています。それがGoogle Workspace管理者認定の役割です。

新問題 53
The CFO just informed you that one of their team members wire-transferred money to the wrong account because they received an email that appeared to be from the CFO. The CFO has provided a list of all users that may be responsible for sending wire transfers. The CFO also provided a list of banks the company sends wire transfers to. There are no external users that should be requesting wire transfers. The CFO is working with the bank to resolve the issue and needs your help to ensure that this does not happen again.
What two actions should you take? (Choose two.)

Configure objectionable content to reject messages with the words “wire transfer.”

Verify that DMARC, DKIM, and SPF records are configured correctly for your domain.

Create a rule requiring secure transport for all messages regarding wire transfers.

Add the sender of the wire transfer email to the blocked senders list.

Enable all admin settings in Gmail’s safety > spoofing and authentication.

新問題 54
Madeupcorp.com is in the process of migrating from a third-party email system to Google Workspace. The VP of Marketing is concerned that her team already administers the corporate AdSense, AdWords, and YouTube channels using their @madeupcorp.com email addresses, but has not tracked which users have access to which service. You need to ensure that there is no disruption.
What should you do?

Run the Transfer Tool for Unmanaged users.

Use a Google Form to survey the Marketing department users.

Assure the VP that there is no action required to configure Google Workspace.

Contact Google Enterprise Support to identify affected users.

新問題 55
You need to grant a specific set of users in your company access to YouTube, and you want to restrict their access to Merchant Center. What should you do?

Enable YouTube for all users in the company. Individually restrict access to Merchant Center for specific Groups or organizational units (OUs).

Create YouTube and Merchant Center as custom web apps. Apply access policies at the Group or organizational unit (OU) level.

Contact Google Support and request that they enable YouTube access for the specific set of users and restrict their access to Merchant Center.

Enable access to YouTube at the Group or organizational unit (OU) level for the subset of users.Disable access to Merchant Center.

新問題 56
A user joined your organization and is reporting that every time they start their computer they are asked to sign in. This behavior differs from what other users within the organization experience. Others are prompted to sign in biweekly. What is the first step you should take to troubleshoot this issue for the individual user?

Reset the user’s sign-in cookies

Confirm that this user has their employee ID populated as a sign-in challenge.

Check the session length duration for the organizational unit the user is provisioned in.

Verify that 2-Step Verification is enforced for this user.

新問題 57
Your cyber security team has requested that all email destined for external domains be scanned for credit card numbers, and if found, the email must be encrypted using your cloud-based third-party encryption provider. You are responsible for configuring to meet this request.
What should you do?

Create a content compliance rule on outbound mail and internal-sending mail using the predefined rule for credit card numbers, and add a custom header that your third-party encryption provider can scan for and encrypt.

Create a content compliance rule on outbound mail using the predefined rule for credit card numbers, and check “Encrypt message if not encrypted”.

Create a content compliance rule on outbound mail using the predefined rule for credit card numbers, and add a custom header that your third-party encryption provider can scan for and encrypt.

Create a content compliance rule on outbound mail using the predefined rule for credit card numbers, and check “Change route” to send to your third-party encryption provider to encrypt.

新問題 58
You work for a midsize organization Your compliance and audit learn sees that users are frequently resetting their passwords You must provide accurate information and ensure that the compliance team is informed every time a user changes their password What should you do?

Create a new alert by using user log events and check that event Login type is Google password and include the compliance team in the email notifications

Check the User’s password changed alert in the alert center and include the compliance team in the email notifications

Disable user account recovery so users must contact you before a reset

Enable user account recovery and forward any alert to the compliance team through the alert center

新問題 59
An employee at your organization is experiencing video call issues in Google Meet and they were unable to resolve the issues by themselves You need to troubleshoot the issue What should you do first?

View the Meet quality report of the employee

Ask your network administrator to add the dedicated Meet IP address range for your users

Restart the device of the employee

Check the Meet settings of the employee

新問題 60
A new user at your organization is unable to access Google Meet. You have verified that the user’s account is active and the correct licenses are assigned. You need to resolve the access issue. What should you do?

Check the user’s browser settings to ensure that Meet is not blocked.

Instruct the user to clear their browser’s cache and cookies.

Restart the user’s computer to refresh their network connection.

Verify that Meet is enabled as a service for the user’s account in the Admin console.

新問題 61
Your company has a globally distributed remote work team. You want to ensure all team members adhere to the company’s data security policies and only access authorized systems based on their location and role.
What should you do?

Create and enforce data loss prevention (DLP) rules to control data sharing.

Set up and mandate the use of a company-wide VPN for all remote access.

Implement two-factor authentication for all remote team members.

Configure access control policies with conditional access.

To ensure that a globally distributed remote work team adheres to data security policies and only accesses authorized systems based on their location and role, you should configure access control policies with conditional access. Conditional access allows you to define rules that grant or block access to resources based on various factors, including the user’s location, the device they are using, their role, and the application they are trying to access.
Here’s why option D is the most comprehensive solution for the stated requirements and why the others address only parts of the problem:
D). Configure access control policies with conditional access.
Conditional access is a security framework that evaluates multiple signals before granting access to resources.
By implementing conditional access policies, you can:Control access based on location: Restrict access to certain systems or data based on the geographic location of the user.
Control access based on role: Ensure that only users with specific roles have access to certain applications or data.
Enforce device compliance: Require users to access resources only from company-managed or compliant devices.
Implement multi-factor authentication (MFA): Require additional verification steps based on the context of the access attempt.
Conditional access provides a granular and dynamic way to enforce security policies based on the specific context of each access request, aligning with the goal of allowing access only to authorized systems based on location and role while maintaining data security.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on “Context-Aware Access” (which is Google’s implementation of conditional access) explains how to set up policies based on user attributes (like group membership/role), device security status, and network location. This documentation details how to create access levels and assign them to applications based on specific conditions, ensuring that access is granted only when the requirements are met.
A). Create and enforce data loss prevention (DLP) rules to control data sharing.
DLP rules are crucial for preventing sensitive data from being shared inappropriately. However, they primarily focus on controlling what users can do with data after they have gained access. DLP does not, by itself, control who can access which systems based on their location and role. It’s a complementary security layer but not the primary solution for access control based on these factors.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on Data Loss Prevention (DLP) explains how to create rules to prevent the sharing of sensitive information. It focuses on the content of the data and user actions related to sharing, not on controlling initial access based on location and role.
B). Set up and mandate the use of a company-wide VPN for all remote access.
A VPN (Virtual Private Network) can secure the connection between remote users and the company network by encrypting traffic and potentially routing it through company-controlled servers. While it can enhance security and provide a consistent network origin, it does not inherently control access based on the user’s role or their geographic location (unless the VPN infrastructure is configured to enforce such restrictions, which would be part of a broader access control strategy). Mandating a VPN is a good security practice but doesn’t fully address the need for role-based and location-aware access control.
Associate Google Workspace Administrator topics guides or documents reference: Documentation on VPNs and remote access might be mentioned in the context of securing connections, but it’s not the primary mechanism for implementing granular access control based on user attributes and location within Google Workspace’s administrative framework.
C). Implement two-factor authentication for all remote team members.
Two-factor authentication (2FA) adds an extra layer of security by requiring users to provide two forms of identification 1 before gaining access. This significantly reduces the risk of unauthorized access 2 due to compromised passwords. While 2FA is a critical security measure for remote teams, it doesn’t, by itself, control which systems users can access based on their location and role. It verifies the user’s identity but not the context of their access attempt in terms of location or role-based authorization.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help strongly recommends enabling 2-Step Verification (Google’s implementation of 2FA) for enhanced security. However, it is primarily focused on user authentication, not on contextual access control based on location and role.
Therefore, the most comprehensive solution to ensure adherence to data security policies and control access based on location and role for a globally distributed remote work team is to configure access control policies with conditional access. This framework allows for the creation of context-aware rules that take into account various factors to determine whether to grant or block access to resources.

新問題 62
You are in the middle of migrating email from on-premises Microsoft Exchange to Google Workspace. Users that you have already migrated are complaining of messages from internal users going into spam folders. What should you do to ensure that internal messages do not go into Gmail spam while blocking spoofing attempts?

Train users to click on Not Spam button for emails.

Add all users of your domain to an approved sender list.

Force TLS for your domain.

Ensure that your inbound gateway is configured with all of your Exchange server IP addresses.

新問題 63
Your chief compliance officer is concerned about API access to organization data across different cloud vendors. He has tasked you with compiling a list of applications that have API access to Google Workspace data, the data they have access to, and the number of users who are using the applications.
How should you compile the data being requested?

Review the authorized applications for each user via the Google Workspace Admin panel.

Create a survey via Google forms, and collect the application data from users.

Review the token audit log, and compile a list of all the applications and their scopes.

Review the API permissions installed apps list, and export the list.

新問題 64
Your company has been engaged in a lawsuit, and the legal department has been asked to discover and hold all email for two specific users. Additionally, they have been asked to discover and hold any email referencing
“Secret Project 123.”
What steps should you take to satisfy this request?

Create a Matter and a Hold. Set the Hold to Gmail, set it to the top level Organization, and set the search terms to “secret project 123.” Create a second Hold. Set the second Hold to Gmail, set it to Accounts, and enter: user1 @your-company.com, [email protected]. Save.

Create a Matter and a Hold. Set the Hold to Gmail, set it to Accounts, and set the usernames to:
[email protected], user2@your-company. Set the search terms to: (secret project 123). Save.

Create a Matter and a Hold. Set the Hold to Gmail, set it to Accounts, and enter: user1@your- company.com AND [email protected]. Set the search terms to: secret AND project AND 123.
Save.

Create a Matter and a Hold. Set the Hold to Gmail, set it to Accounts, and set the usernames to:
[email protected], user2@your-company. Set the search terms to secret OR project OR 123.
Save.

新問題 65
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?

Suspicious mobile activity alert.

Suspicious login activity alert.

Leaked password alert.

User sign-in alert.

新問題 66
You are in charge of automating and configuring Google Cloud Directory Sync for your organization. Within the config manager, how can you proactively prevent applying widespread deletions within your Workspace environment if your company’s LDAP undergoes a substantial modification?

Manually run Google Cloud Directory Sync only after performing a simulated sync.

Specify the minimum and maximum number of objects to synchronize in each configuration item.

Configure the tool to delete users only when run from the config manager.

Configure limits for the maximum number of deletions on each synchronization.

新問題 67
After making a recent migration to Google Workspace, you updated your Google Cloud Directory Sync configuration to synchronize the global address list. Users are now seeing duplicate contacts in their global directory in Google Workspace. You need to resolve this issue.
What should you do?

Train users to use Google Workspace’s merge contacts feature.

Enable directory contact deduplication in the Google Workspace Admin panel.

Update shared contact search rules to exclude internal users.

Create a new global directory, and delete the original.

新問題 68
You want to create a list of IP addresses that are approved to send email to your domain. To accomplish this, what section of the Google Workspace Admin console should you update?

Bypass spam filter

Content compliance rule

Approved email denylist

Email allowlist

新問題 69
The human resources department notified you of a legal investigation that was started for an employee in the finance department. You need to ensure that this employee’s Google Drive data is preserved for at least one year and does not get deleted by the user or by other means. The Google Vault default retention rules for Drive are set for five years. What should you do?

Change the Vault default retention rule to one year instead of five.

Place the employee into a separate organizational unit (OU). Create a custom one-year retention rule for this OU.

Create a hold in Vault for the employee’s Drive.

Confirm that the Vault default retention rule is set for five years.

When there’s a legal investigation, the priority is to ensure that relevant data is preserved and not deleted, regardless of retention policies or user actions. A “hold” (also known as a litigation hold or legal hold) in Google Vault is specifically designed for this purpose. It overrides all retention rules (both default and custom) and prevents any data covered by the hold from being purged, even if a user attempts to delete it.
Here’s why the other options are not the correct or best solution:
* A. Change the Vault default retention rule to one year instead of five. Changing the default retention rule would affect all Drive data in your organization, not just this specific employee’s. It’s a broad change and not suitable for a targeted legal hold. Moreover, it wouldn’t guarantee preservation against user deletions.
* B. Place the employee into a separate organizational unit (OU). Create a custom one-year retention rule for this OU. While creating custom retention rules for OUs is possible, it’s not the primary mechanism for a legal hold. Retention rules define when data can be deleted, but a hold prevents deletion irrespective of the retention period. If the employee deletes the data, a retention rule won’t stop it from moving to trash (and eventually being purged) unless a hold is in place. Furthermore, a one-year retention rule isn’t the goal; the goal is to preserve for “at least one year” (meaning indefinitely until the hold is released). The default five-year rule is already longer than one year, but doesn’t override user deletion.
* D. Confirm that the Vault default retention rule is set for five years. The question states that the default retention rule for Drive is already set for five years. While this is good for general data retention, it does not prevent a user from deleting their own files from Drive, nor does it specifically address the need for a legal hold where data must be absolutely preserved. A default retention rule does not override user deletion or ensure data preservation for legal purposes.
References from Google Workspace Administrator:
* Holds in Google Vault: This is the core concept. Holds prevent data from being purged from Google systems, regardless of retention rules or user actions, until the hold is released. They are specifically used for legal discovery or investigation purposes.
Reference: Google Workspace Admin Help: Place holds on user accounts
Reference: Google Workspace Admin Help: Holds prevent data from being purged (This page explicitly states that “Holds override retention rules-even if the retention period expires, data on hold is preserved.”) Retention rules in Google Vault: While relevant to data management, retention rules define when data can be deleted if no hold applies. They do not prevent users from deleting data or ensure preservation for legal holds.
Reference: Google Workspace Admin Help: How retention works with Google services

新問題 70
As the Workspace Administrator, you have been asked to configure Google Cloud Directory Sync (GCDS) in order to manage Google Group memberships from an internal LDAP server. However, multiple Google Groups must have their memberships managed manually. When you run the GCDS sync, you notice that these manually managed groups are being deleted. What should you do to prevent these groups from being deleted?

In the GCDS configuration manager, update the group deletion policy setting to “don’t delete Google groups not found in LDAP.”

Use the Directory API to check and update the group’s membership after the GCDS sync is completed.

Confirm that the base DN for the group email address attribute matches the base DN for the user email address attribute.

In the user attribute settings of the GCDS configuration manager options, set the Google domain users deletion/suspension policy to “delete only active Google domain users not found in LDAP.”

Google-Workspace-Administrator試験合格を準備するため今すぐ弊社のWorkspace Administrator試験パッケージお試そう：https://www.passtest.jp/Google/Google-Workspace-Administrator-shiken.html