Loading...
No results found.

    Set Up an App Dev Environment on Google Cloud

    Test and share your knowledge with our community!
    done
    Get access to over 700 hands-on labs, skill badges, and courses

    Set Up an App Dev Environment on Google Cloud: Challenge Lab

    Lab 1 hour universal_currency_alt 1 Credit show_chart Introductory
    info This lab may incorporate AI tools to support your learning.
    Test and share your knowledge with our community!
    done
    Get access to over 700 hands-on labs, skill badges, and courses

    GSP315

    Google Cloud self-paced labs logo

    Introduction

    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!

    This lab is recommended for students who have enrolled in the Set Up an App Dev Environment on Google Cloud skill badge. Are you ready for the challenge?

    Setup

    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 junior cloud engineer role with Jooli inc. So far you have been helping teams create and manage Google Cloud resources.

    You are expected to have the skills and knowledge for these tasks, so don’t expect step-by-step guides.

    Your challenge

    You are asked to help a newly formed development team with some of their initial work on a new project around storing and organizing photographs, called Memories. You have been asked to assist the Memories team with initial configuration for their application development environment.

    You receive the following request to complete the following tasks:

    • Create a bucket for storing the photographs.
    • Create a Pub/Sub topic that will be used by a Cloud Run Function you create.
    • Create a Cloud Run Function.
    • Remove the previous cloud engineer’s access from the memories project.

    Some Jooli Inc. standards you should follow:

    • Create all resources in the region and zone, unless otherwise directed.
    • Use the project VPCs.
    • Naming is normally team-resource, e.g. an instance could be named kraken-webserver1
    • Allocate cost effective resource sizes. Projects are monitored and excessive resource use will result in the containing project's termination (and possibly yours), so beware. This is the guidance the monitoring team is willing to share; unless directed, use e2-micro for small Linux VMs and e2-medium for Windows or other applications such as Kubernetes nodes.

    Each task is described in detail below, good luck!

    Task 1. Create a bucket

    You need to create a bucket called for the storage of the photographs. Ensure the resource is created in the region and zone.

    Click Check my progress to verify the objective. Create a bucket called

    Task 2. Create a Pub/Sub topic

    Create a Pub/Sub topic called for the Cloud Run Function to send messages.

    Click Check my progress to verify the objective. Create a Pub/Sub topic called

    Task 3. Create the thumbnail Cloud Run Function

    Create a Cloud Run Function that will to create a thumbnail from an image added to the bucket. Ensure the Cloud Run Function is using the Cloud Run function environment (which is 2nd generation). Ensure the resource is created in the region and zone.

    1. Create a Cloud Run Function called
    Note: The Cloud Run Function is required to executes every time an object is created in the bucket created in Task 1. During the process Cloud Run Function may request permission to enable APIs. Please enable each of the required APIs as requested.
    1. Make sure you set the Entry point (Function to execute) to and Trigger to Cloud Storage.

    2. Add the following code to the index.js:

    const functions = require('@google-cloud/functions-framework'); const crc32 = require("fast-crc32c"); const { Storage } = require('@google-cloud/storage'); const gcs = new Storage(); const { PubSub } = require('@google-cloud/pubsub'); const imagemagick = require("imagemagick-stream"); functions.cloudEvent('{{{ project_0.startup_script.function }}}', cloudEvent => { const event = cloudEvent.data; console.log(`Event: ${event}`); console.log(`Hello ${event.bucket}`); const fileName = event.name; const bucketName = event.bucket; const size = "64x64" const bucket = gcs.bucket(bucketName); const topicName = "{{{ project_0.startup_script.topic }}}"; const pubsub = new PubSub(); if ( fileName.search("64x64_thumbnail") == -1 ){ // doesn't have a thumbnail, get the filename extension var filename_split = fileName.split('.'); var filename_ext = filename_split[filename_split.length - 1]; var filename_without_ext = fileName.substring(0, fileName.length - filename_ext.length ); if (filename_ext.toLowerCase() == 'png' || filename_ext.toLowerCase() == 'jpg'){ // only support png and jpg at this point console.log(`Processing Original: gs://${bucketName}/${fileName}`); const gcsObject = bucket.file(fileName); let newFilename = filename_without_ext + size + '_thumbnail.' + filename_ext; let gcsNewObject = bucket.file(newFilename); let srcStream = gcsObject.createReadStream(); let dstStream = gcsNewObject.createWriteStream(); let resize = imagemagick().resize(size).quality(90); srcStream.pipe(resize).pipe(dstStream); return new Promise((resolve, reject) => { dstStream .on("error", (err) => { console.log(`Error: ${err}`); reject(err); }) .on("finish", () => { console.log(`Success: ${fileName} → ${newFilename}`); // set the content-type gcsNewObject.setMetadata( { contentType: 'image/'+ filename_ext.toLowerCase() }, function(err, apiResponse) {}); pubsub .topic(topicName) .publisher() .publish(Buffer.from(newFilename)) .then(messageId => { console.log(`Message ${messageId} published.`); }) .catch(err => { console.error('ERROR:', err); }); }); }); } else { console.log(`gs://${bucketName}/${fileName} is not an image I can handle`); } } else { console.log(`gs://${bucketName}/${fileName} already has a thumbnail`); } });
    1. Add the following code to the package.json:
    { "name": "thumbnails", "version": "1.0.0", "description": "Create Thumbnail of uploaded image", "scripts": { "start": "node index.js" }, "dependencies": { "@google-cloud/functions-framework": "^3.0.0", "@google-cloud/pubsub": "^2.0.0", "@google-cloud/storage": "^5.0.0", "fast-crc32c": "1.0.4", "imagemagick-stream": "4.1.1" }, "devDependencies": {}, "engines": { "node": ">=4.3.2" } }

    Verify the thumbnail was successfully created.

    Note: If you get a permission denied error stating it may take a few minutes before all necessary permissions are propagated to the Service Agent, wait a few minutes and try again. Ensure you have the relevant roles (Eventarc Service Agent, Eventarc Event Receiver, Service Account Token Creator, and Pub/Sub Publisher) assigned to the correct service accounts.

    Click Check my progress to verify the objective. Verify the Cloud Run Function

    Task 4. Test the Infrastructure

    You must upload one JPG or PNG image into the bucket

    1. Upload a PNG or JPG image to bucket.
    Note: Alternatively Download this image https://storage.googleapis.com/cloud-training/gsp315/map.jpg to your machine. Then upload it to the bucket.
    1. You will see a thumbnail image appear shortly afterwards (use REFRESH in the bucket details).

    Task 5. Remove the previous cloud engineer

    You will see that there are two users defined in the project.

    • One is your account ( with the role of Owner).
    • The other is the previous cloud engineer ( with the role of Viewer).
    1. Remove the previous cloud engineer’s access from the project.

    Click Check my progress to verify the objective. Remove the previous cloud engineer

    Congratulations!

    Set Up an App Dev Environment on Google Cloud

    Next steps / Learn more

    This skill badge is part of Google's Perform Foundational Infrastructure Tasks in Google Cloud and Cloud Architect learning paths. If you have already completed the other skill badges in your learning path, search the Google Cloud Skills Boost catalog for other skill badges in which you can enroll.

    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 September 10, 2024

    Lab Last Tested September 10, 2024

    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.

    Previous Next

    This content is not currently available

    We will notify you via email when it becomes available

    Great!

    We will contact you via email if it becomes available

    Preview