Managing Cymbal Superstore’s cloud solutions

1. Managing Cymbal Superstore’s cloud solutions

Now that Cymbal Superstore's cloud solutions have been deployed and implemented, your role as an Associate Cloud Engineer shifts focus to maintaining successful operations. Let's explore what that means. In deploying and implementing Cymbal Superstore's cloud architecture, you needed to know how to work with various compute, storage, and networking resources on Google Cloud. To ensure successful operations, an Associate Cloud Engineer needs the knowledge and skills to manage the resources used in an organization's cloud solutions. You also need to be able to use Google Cloud Observability for monitoring and logging. Cymbal Superstore's supply chain management app is made of up of resources implemented close to their headquarters in Minneapolis, Minnesota. It is architected using Compute Engine. Managed instance groups let the application scale automatically and remain available across zonal outages. Sometimes, the instance template that that group is based on might need to be changed. Some reasons why you might want to do this include the following: Updating the operating system of your instances. Conducting A/B or canary testing of capability upgrades. Changing the disk type, or attached disks, attached to your instances. Once you do update the template, you'll need to ensure the change is propagated to all the VM instances in the group. Cymbal Superstore's ecommerce app is architected using containers deployed to GKE pods. As an Associate Cloud Engineer on the ecommerce team, you might be asked to configure and monitor external connectivity. An external http(s) load balancer is a solution that advertises a single global IP, provides content close to your end user, and forwards content to backends that are available globally. Cymbal Superstore's transportation management app uses Cloud Run functions to monitor incoming sensor data and implements a Dataflow pipeline that uses a sink to write data to Bigtable. As an Associate Cloud Engineer, it is common to provide information about the sources and sinks required by a pipeline to the data engineer responsible for developing it. You also need to know how to monitor your incoming data stream and manage your Cloud Run function instances. Let's specifically discuss how you might set up the resources required to query that data on a regular basis. What would it involve? Let's think about Cymbal Superstore's transportation management app. You can use BigQuery sql to query your Bigtable data by defining a permanent external table using the Google Cloud console or the bq command line tool. You do this by creating a table definition file, which includes the uri for the table in Bigtable, and information about the column families and the columns defined in the table. The entries for the table definition are written in JSON. Next, you create the external table reference with a bq mk command. On screen, you'll see an example of what it might look like for our Cymbal Superstore example. Then, you can submit the query using BigQuery sql.

2. Let's practice!

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.