三叉戟

本页面只读。您可以查看源文件，但不能更改它。如果您觉得这是系统错误，请联系管理员。
# 第5章 GWS部署
部署分为3个阶段
  - Core IT
  - Early Adopters
  - Global Go-Live
大概需要3个月的时间，CoreIT是第一阶段，主要是25人以下的小团队确定测试项目，熟悉GWS系统，第二阶段也占用1个月时间，主要是验证迁移的有效性，获得FB，测试变更计划，最后阶段，是全面展开

## GCDS
  * GCDS is installed on a local server, connect to local directory
  * Data is extracted as a list from AD
  * GCDS connects to GWS and generates a list of objects to synchronize
  * GCDS compares the lists and updates the Google domain to match the AD data

GWS structure will not reflect AD hierarchy, so don't use OU sync.

## 部署方针
分为4部分
  - Users
  - Groups
  - Shared contacts
  - Calendar Resources

## 测试1
<q>How does GCDS support password synchronization from Active Directory?</q>
  - GCDS monitors Active Directory for changes to a user’s password and then pushes the change up when the next synchronization operation occurs.
  - **GCDS does not support the Active Directory password format. Customers should deploy G Suite Password Sync to support password changes.**
  - GCDS continuously monitors Active Directory for changes to a user’s password and then pushes the change up immediately.

<q>What is Google’s preferred method for verifying domain ownership?</q>
  - Add a metatag to your web site’s home page.
  - Send Google a copy of your DNS invoice stating you own the domain.
  - **Add a TXT record to your DNS records.**
  - Add a CNAME record to your DNS records.

<q>How does Google’s recommend Core IT users to book calendar resources?</q>
  - Manually create all resources in Google Workspace as part of the Core IT phase so they can book resources from Google Calendar.
  - Core IT users should not be using Google Calendar. They should continue to use the legacy system calendar and resource booking system.
  - Deploy GCDS as part of the Core IT phase so resources can be synchronized and they can be used from the legacy system and Google Workspace.
  - **Ask Core IT users to book resources in the legacy platform.**

<q>How does Google Cloud Directory Sync synchronize directories?</q>
  - **GCDS ensures the Google directory matches the local LDAP directory by pushing updates to Google only.**
  - GCDS performs a two way sync so changes made in either directory are updated in the other. Conflicts are handled by applying the most recent change made to an object.
  - The GCDS administrator can choose to make either the Google directory or the local LDAP directory the master directory.
  - GCDS ensures the LDAP directory matches the Google directory by pulling changes down from Google only.

## 测试2
<q>A message is sent to Gmail to a valid user in your organization but the user has not yet been provisioned in Google Workspace. How can you ensure this mail is not lost and can be delivered to the intended recipient?</q>
  - **Configure the default routing policy in Google Workspace to catch any unrecognized addresses and route those back to the legacy system.**
  - During the deployment, ensure all messages sent to Google are also dual delivered to the legacy system.
  - Configure a routing policy at the Legacy Users OU level.
  - Route unrecognized addresses to a Google group.

<q>During the Core IT phase how can you ensure that a message sent from a user on the legacy platform to a Core IT user is correctly delivered to their Gmail inbox?</q>
  - Ask your legacy system users to enter the recipient’s new Google Workspace address into the To header of the message.
  - **Setup a domain alias in Google Workspace and create forwarding rules for each Core IT user to forward intradomain messages to the shadow domain in Google Workspace.**
  - Any of the options here.
  - Configure split delivery and route all messages to Google.

<q>How can you ensure that messages forwarded from your legacy mail servers to Gmail are not classified as spam by Google?</q>
  - **Configure the inbound gateway setting in Google Workspace.**
  - Allowlist your mail server in Google Workspace.
  - Ensure outbound mail is routed through your own Spam server before forwarding to Google.
  - All of the options here.

<q>At what phase in the deployment process would you typically configure your MX records to point to the Google servers?</q>
  - Global Go-Live
  - **Early Adopter**
  - Core IT

<q>After a Google Workspace deployment, the organization’s MX records will be pointing to Google’s mail servers. Mail is then delivered to each user’s Gmail inbox. What type of mail delivery is this?</q>
  - Dual Delivery
  - **Direct Delivery**
  - Split Delivery

## 测试3
<q>When considering what data to migrate (mail, calendar and contacts) for the Global Go-Live, which of the following is considered best practice?</q>
  - **Migrate only what you need.**
  - Migrate everything.
  - Migrate nothing.

<q>Which of the following are considered best practices for data migration?</q>
  - **All of the options here.**
  - Migrate calendar and contacts for users just before they switch to Google Workspace.
  - Locate your migration servers alongside/close to your legacy servers.
  - Migrate local archives such as PST files after deployment.

<q>Which Google tool would you use to perform a server side migration from Microsoft Exchange to Google Workspace?</q>
  - **GWMME**
  - GWMMO
  - GWMHN
  - Data Migration Service

## 测试4
<q>During a deployment, what calendar coexistence challenges will your users face?</q>
  - How to book resources across both platforms.
  - How to view the attendee status of a user on the other platform.
  - How to check the availability (free/busy status) of a user on the other platform.
  - **All of the options here.**

<q>What are options for adding Shared Contacts to Google Workspace?</q>
  - **All of the options here.**
  - Google Workspace Marketplace tools.
  - GCDS.
  - Shared Contacts API.

<q>Google recommends the use of calendar connectors during a deployment.</q>
  - **True**
  - False

## 测试5
<q>What best describes the Early Adopters?</q>
  - People who are resistant to change.
  - People who are highly willing to take risks.
  - People who look at change skeptically.
  - **People who tend to be opinion formers in the organization**

<q>In a typical organization, what is the percentage of people who can adapt to change independently?</q>
  - Between 20% and 50%.
  - Between 50% and 80%.
  - More than 80%.
  - **Less than 20%**

<q>Why do some projects fail?</q>
  - Lack of executive support.
  - Assuming that everything will work out.
  - **All of the options here.**
  - Incorrectly thinking that it is all about technology.