Google Cloud Console Cheat Sheet

• Google Cloud Console is a web admin interface to manage your Google cloud infrastructure.

Features

• You can create projects on Google Cloud Console.
• With Cloud Console, you can quickly find and check the health of all your cloud resources in one place, including virtual machines, network settings, and data storage.
• Logging
  • Manage and audit user access to project resources.
  • Track down production issues quickly by viewing logs.
• You can explore the Google Cloud Marketplace and launch cloud solutions with just a few clicks.
• Billing
  • View a detailed billing breakdown of your bills.
  • Set spending budgets to avoid unexpected surprises
• Cloud Console enables you to connect to your virtual machines via Cloud Shell. You can quickly handle admin tasks using this instant-on Linux machine equipped with your favorite tools including Google Cloud SDK preconfigured and authenticated.

Pricing

• Cloud Console is available at no cost to Google Cloud Platform customers.

Validate Your Knowledge

Question 1

Your company just deployed a major version release of its web application to Google App Engine. A few hours later, users started reporting a critical issue with the latest release. You decided to quickly revert back to the previous version of the application while your team is investigating the issue.

What should you do?

1. Use the Cloud Console to go to the App Engine Versions page. Reroute 100% of the traffic to the previous working version of the application.
2. On the Cloud Shell, execute the command gcloud components restore.
3. Use the Cloud Console to go to the App Engine Versions page. Choose the previous web application version to split the traffic between the current and previous versions.
4. Deploy the working version of your web app as a separate application. Go to App Engine settings and configure the application to route 100% of the traffic to the original version.

Question 2

1. Using the Cloud Console, create a Compute Engine instance. Configure the Primary internal IP as a static internal IP address and set it to 10.146.0.17.
2. Using the Cloud Console, create a Compute Engine instance. Configure the External IP as a static IP address and set it to 10.146.0.17.
3. Do not assign an IP while creating the licensing server on Compute Engine to automatically get an ephemeral internal IP address.
4. Start the licensing server with an automatically generated ephemeral IP address. Afterward, promote it to a static external IP address set to 10.0.146.0.17.

Show me the answer!

Correct Answer: 1

Static internal IPs provide the ability to reserve internal IP addresses from the IP range configured in the subnet, then assign those reserved internal addresses to resources as needed. Reserving an internal IP address takes that address out of the dynamic allocation pool and prevents it from being used for automatic allocations. Reserving static internal IP addresses requires specific IAM permissions so that only authorized users can reserve a static internal IP address.

With the ability to reserve static internal IP addresses, you can always use the same IP address for the same resource even if you have to delete and recreate the resource.

We need to make sure that the configuration of the application connecting to the licensing server does not change. Moreover, the IP assigned to an instance is a private IP address used for internal networking. This means that reserving a static internal IP is the best option.

Hence the correct answer is: Using the Cloud Console, create a Compute Engine instance. Configure the Primary internal IP as a static internal IP address and set it to 10.146.0.17.

The option that says: Using the Cloud Console, create a Compute Engine instance. Configure the External IP as a static IP address and set it to 10.146.0.17. is incorrect because 10.146.0.17 is not an external IP address but an internal IP address that belongs to the private IP address range advised by Google.

The option that says: Do not assign an IP while creating the licensing server on Compute Engine to automatically get an ephemeral internal IP address is incorrect because an ephemeral address lasts only until a VM is running. Once the VM is stopped or needs to be recreated, the new VM will use a new ephemeral IP which will force you to change the IP configured on the application.

The option that says: Start the licensing server with an automatically generated ephemeral IP address. Afterward, promote it to a static external IP address 10.0.146.0.17 is incorrect. You don’t need a static external IP address since the IP 10.0.146.0.17 belongs to a private subnet. What you need is a static internal IP address instead.

References:
https://cloud.google.com/compute/docs/ip-addresses#reservedaddress
https://cloud.google.com/vpc/docs/ip-addresses

Note: This question was extracted from our Google Certified Associate Cloud Engineer Practice Exams.

For more Google Cloud practice exam questions with detailed explanations, check out the Tutorials Dojo Portal:

Google Cloud Console Cheat Sheet Reference:

https://cloud.google.com/cloud-console