Chargement...
Aucun résultat.

    Google Cloud Skills Boost

    Cloud Architect Accelerated Learning Path for Azure professionals navigate_next Set Up an App Dev Environment on Google Cloud: Challenge Lab
    Quick tip: Review the prerequisites before you run the lab
    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.
    Testez vos connaissances et partagez-les avec notre communauté
    done
    Accédez à plus de 700 ateliers pratiques, badges de compétence et cours

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

    Atelier 1 heure universal_currency_alt 1 crédit show_chart Débutant
    info Cet atelier peut intégrer des outils d'IA pour vous accompagner dans votre apprentissage.
    Testez vos connaissances et partagez-les avec notre communauté
    done
    Accédez à plus de 700 ateliers pratiques, badges de compétence et cours

    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 are made available to you.

    This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials 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 (recommended) or private browser window to run this lab. This prevents 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: Use only the student account for this lab. If you use a different Google Cloud account, you may incur charges to that 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 the 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 (2nd generation) called using Node.js 22.
    Note: The Cloud Run Function is required to execute 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 or request permission to grant roles to service accounts. Please enable each of the required APIs and grant roles 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 { Storage } = require('@google-cloud/storage'); const { PubSub } = require('@google-cloud/pubsub'); const sharp = require('sharp'); functions.cloudEvent('{{{ project_0.startup_script.function }}}', async cloudEvent => { const event = cloudEvent.data; console.log(`Event: ${JSON.stringify(event)}`); console.log(`Hello ${event.bucket}`); const fileName = event.name; const bucketName = event.bucket; const size = "64x64"; const bucket = new Storage().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 const filename_split = fileName.split('.'); const filename_ext = filename_split[filename_split.length - 1].toLowerCase(); const filename_without_ext = fileName.substring(0, fileName.length - filename_ext.length - 1); // fix sub string to remove the dot if (filename_ext === 'png' || filename_ext === 'jpg' || filename_ext === 'jpeg') { // only support png and jpg at this point console.log(`Processing Original: gs://${bucketName}/${fileName}`); const gcsObject = bucket.file(fileName); const newFilename = `${filename_without_ext}_64x64_thumbnail.${filename_ext}`; const gcsNewObject = bucket.file(newFilename); try { const [buffer] = await gcsObject.download(); const resizedBuffer = await sharp(buffer) .resize(64, 64, { fit: 'inside', withoutEnlargement: true, }) .toFormat(filename_ext) .toBuffer(); await gcsNewObject.save(resizedBuffer, { metadata: { contentType: `image/${filename_ext}`, }, }); console.log(`Success: ${fileName} → ${newFilename}`); await pubsub .topic(topicName) .publishMessage({ data: Buffer.from(newFilename) }); console.log(`Message published to ${topicName}`); } 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": "^6.11.0", "sharp": "^0.32.1" }, "devDependencies": {}, "engines": { "node": ">=4.3.2" } } 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 appropriate roles (Eventarc Service Agent, Eventarc Event Receiver, Service Account Token Creator, and Pub/Sub Publisher) assigned to the correct service accounts.

    Test the function

    • Upload a PNG or JPG image of your choice to the bucket.
    Note: Alternatively, download this image https://storage.googleapis.com/cloud-training/gsp315/map.jpg to your machine. Then, upload it to the bucket.

    You will see a thumbnail image appear shortly afterwards (use REFRESH on the bucket details page).

    After you upload the image file, you can click to check your progress below. You do not need to wait for the thumbnail image to be created.

    Optional: If the function deployed successfully and you do not see the thumbnail image in the bucket, you can check that the Triggers tab displays the trigger information that you previously provided for the function, which may not have saved correctly if you previously encountered errors. If you do not see the Cloud Storage trigger in the Triggers tab of the function, you can recreate the trigger (see the documentation page titled Create a trigger for services), and then upload a new file again to test again (refresh the page after adding a new file).

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

    Task 4. 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 March 8, 2025

    Lab Last Tested March 8, 2025

    Copyright 2025 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.

    Before you begin

    1. Labs create a Google Cloud project and resources for a fixed time
    2. Labs have a time limit and no pause feature. If you end the lab, you'll have to restart from the beginning.
    3. On the top left of your screen, click Start lab to begin

    Use private browsing

    1. Copy the provided Username and Password for the lab
    2. Click Open console in private mode

    Sign in to the Console

    1. Sign in using your lab credentials. Using other credentials might cause errors or incur charges.
    2. Accept the terms, and skip the recovery resource page
    3. Don't click End lab unless you've finished the lab or want to restart it, as it will clear your work and remove the project

    Ce contenu n'est pas disponible pour le moment

    Nous vous préviendrons par e-mail lorsqu'il sera disponible

    Parfait !

    Nous vous contacterons par e-mail s'il devient disponible

    One lab at a time

    Confirm to end all existing labs and start this one

    Use private browsing to run the lab

    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.