ARC125

Overview

In a challenge lab you’re given a scenario and a set of tasks. Instead of following step-by-step instructions, you will use the skills learned from the labs in the course to figure out how to complete the tasks on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly.

When you take a challenge lab, you will not be taught new Google Cloud concepts. You are expected to extend your learned skills, like changing default values and reading and researching error messages to fix your own mistakes.

To score 100% you must successfully complete all tasks within the time period!

Setup and requirements

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

• Access to a standard internet browser (Chrome browser recommended).

Note: Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.

• Time to complete the lab---remember, once you start, you cannot pause a lab.

Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your account.

Challenge scenario

You are just starting your cloud engineer role. So far you have been helping teams to use the Google Cloud services required for various projects. One of the current project requirements is to use the Cloud Storage API to create new buckets, upload files, copy files between buckets, make objects publicly accessible, and delete files and buckets.

You are expected to have the skills and knowledge for the tasks that follow.

Your challenge

For this challenge, you have been tasked with creating buckets, uploading a file, copying a file to another bucket, making an object (file) publicly accessible, and deleting the original file and bucket using the Cloud Storage JSON/REST API.

You need to perform the following tasks using the Cloud Storage JSON/REST API:

• Create a bucket.
• Upload an object file to a Cloud Storage bucket.
• Copy the file to another bucket.
• Make the file publicly accessible.
• Delete the file from the first Cloud Storage bucket.
• Delete the first Cloud Storage bucket.

Some standards you should follow:

• Ensure you set an environmental variable for your project ID and obtain an authorization token for the Cloud Storage API that you can use in Cloud Shell. For more information, review the lab titled Introduction to APIs in Google.
• Be sure to perform each task using the Cloud Storage JSON/REST API.

Each task is described in detail below, good luck!

Task 1. Create two Cloud Storage buckets

1. Create a JSON file that contains the following code in the Cloud Shell:

{ "name": "{{{project_0.startup_script.project_id | filled in at lab start}}}-bucket-1", "location": "us", "storageClass": "multi_regional" }

2. Use curl to call the JSON API to create the bucket.

3. Repeat steps one and two to create a second bucket named -bucket-2.

Click Check my progress to verify the objective. Create two Cloud Storage buckets

Task 2. Upload an image file to a Cloud Storage Bucket

1. For this task, save the below image to your computer and give it a name of your choice.

2. In your Cloud Shell session, click on the More menu icon in the top-right corner. Click Upload > Choose File. Select and upload your file. This will add the image to your home directory.

3. Use curl to call the JSON API that uploads the file to the bucket -bucket-1.

Click Check my progress to verify the objective. Upload an image file to a Cloud Storage Bucket

Task 3. Copy a file to another bucket

For this task, use curl to call the JSON API and copy the image file from the Cloud Storage bucket -bucket-1 to a second bucket, -bucket-2.

Click Check my progress to verify the objective. Copy a file to another bucket

Task 4. Make an object (file) publicly accessible

1. Create a JSON file that has the following code:

{ "entity": "allUsers", "role": "READER" }

2. Use curl to call the JSON API and make the object (file) publicly accessible.

Click Check my progress to verify the objective. Make an object (file) publicly accessible

Task 5. Delete the object file and a Cloud Storage bucket (Bucket 1)

For this task, you will do some cleanup.

Now that the file has been copied to the second Cloud Storage bucket -bucket-2, you will delete the object file in the first bucket (Bucket 1) as well as Bucket 1, -bucket-1.

1. Use curl to call the JSON API and delete the file stored in the Cloud Storage bucket -bucket-1.

2. Use curl to call the JSON API and delete the Cloud Storage bucket -bucket-1.

Click Check my progress to verify the objective. Delete the file and Cloud Storage bucket (Bucket 1)

Congratulations!

You have successfully created Cloud Storage buckets, uploaded files, copied objects between buckets, made an object publically accessible, and deleted files and buckets using the JSON REST API.

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated June 12, 2023

Lab Last Tested June 12, 2023

Copyright 2024 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.