You are moving an application that uses MySQL from on-premises to Google Cloud. The application will run on Compute Engine and will use Cloud SQL. You want to cut over to the Compute Engine deployment of the application with minimal downtime and no data loss to your customers. You want to migrate the application with minimal modification. You also need to determine the cutover strategy. What should you do?

• A.1. Stop the on-premises application.
  2.Create a mysqldump of the on-premises MySQL server.
  3.Upload the dump to a Cloud Storage bucket.
  4.Import the dump into Cloud SQL.
  5.Start the application on Compute Engine.
• B.1. Set up Cloud VPN to provide private network connectivity between the Compute Engine application and the on-premises MySQL server.
  2.Stop the on-premises application.
  3.Create a mysqldump of the on-premises MySQL server.
  4.Upload the dump to a Cloud Storage bucket.
  5.Import the dump into Cloud SQL.
  6.Modify the source code of the application to write queries to both databases and read from its local database.
  7.Start the Compute Engine application.
  8.Stop the on-premises application.
• C.1. Set up Cloud VPN to provide private network connectivity between the Compute Engine application and the on-premises MySQL server.
  2.Stop the on-premises application.
  3.Start the Compute Engine application, configured to read and write to the on-premises MySQL server.
  4.Create the replication configuration in Cloud SQL.
  5.Configure the source database server to accept connections from the Cloud SQL replica.
  6.Finalize the Cloud SQL replica configuration.
  7.When replication has been completed, stop the Compute Engine application.
  8.Promote the Cloud SQL replica to a standalone instance.
  9.Restart the Compute Engine application, configured to read and write to the Cloud SQL standalone instance.
• D.1. Set up Cloud SQL proxy and MySQL proxy.
  2.Create a mysqldump of the on-premises MySQL server.
  3.Upload the dump to a Cloud Storage bucket.
  4.Import the dump into Cloud SQL.
  5.Stop the on-premises application.
  6.Start the Compute Engine application.

Comment: *

Name: *

Email: *

Verification: *

You are migrating your on-premises solution to Google Cloud in several phases. You will use Cloud VPN
to maintain a connection between your on-premises systems and Google Cloud until the migration is
completed. You want to make sure all your on-premises systems remain reachable during this period. How
should you organize your networking in Google Cloud?

• A.Use an IP range on Google Cloud that does not overlap with the range you use on-premises for your
  primary IP range and use a secondary range with the same IP range as you use on-premises
• B.Use an IP range on Google Cloud that does not overlap with the range you use on-premises
• C.Use the same IP range on Google Cloud as you use on-premises for your primary IP range and use a
  secondary range that does not overlap with the range you use on-premises
• D.Use the same IP range on Google Cloud as you use on-premises

Comment: *

Name: *

Email: *

Verification: *

For this question, refer to the Mountkirk Games case study
Mountkirk Games needs to create a repeatable and configurable mechanism for deploying isolated application environments. Developers and testers can access each other's environments and resources, but they cannot access staging or production resources. The staging environment needs access to some services from production.
What should you do to isolate development environments from staging and production?

• A.Create a project for development and test and another for staging and production.
• B.Create a network for development and test and another for staging and production.
• C.Create one subnetwork for development and another for staging and production.
• D.Create one project for development, a second for staging and a third for production.

Comment: *

Name: *

Email: *

Verification: *

The application reliability team at your company has added a debug feature to their backend service to send all server events to Google Cloud Storage for eventual analysis. The event records are at least 50 KB and at most
15 MB and are expected to peak at 3,000 events per second. You want to minimize data loss.
Which process should you implement?

• A.* Append metadata to file body.
  * Compress individual files.
  * Name files with serverName-Timestamp.
  * Create a new bucket if bucket is older than 1 hour and save individual files to the new bucket.
  Otherwise, save files to existing bucket
• B.* Batch every 10,000 events with a single manifest file for metadata.
  * Compress event files and manifest file into a single archive file.
  * Name files using serverName-EventSequence.
  * Create a new bucket if bucket is older than 1 day and save the single archive file to the new bucket.
  Otherwise, save the single archive file to existing bucket.
• C.* Compress individual files.
  * Name files with serverName-EventSequence.
  * Save files to one bucket
  * Set custom metadata headers for each object after saving.
• D.* Append metadata to file body.
  * Compress individual files.
  * Name files with a random prefix pattern.
  * Save files to one bucket

Comment: *

Name: *

Email: *

Verification: *

You are designing a mobile chat application. You want to ensure people cannot spoof chat messages, by providing a message were sent by a specific user.
What should you do

• A.Tag messages client side with the originating user identifier and the destination user.
• B.Encrypt the message client side using block-based encryption with a shared key.
• C.Use public key infrastructure (PKI) to encrypt the message client side using the originating user's private key.
• D.Use a trusted certificate authority to enable SSL connectivity between the client application and the server.

Comment: *

Name: *

Email: *

Verification: *