Cloud Shell and gcloud CLI in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Cloud Shell Session Persistence

You start a Cloud Shell session and create a file named notes.txt in your home directory. After 12 hours, you reconnect to Cloud Shell. What will happen to the notes.txt file?

A The file will be there only if you saved it to the /tmp directory.

B The file will be gone because Cloud Shell resets the home directory every time you reconnect.

C The file will still be there because Cloud Shell home directory is persistent across sessions.

D The file will be deleted automatically after 1 hour of inactivity.

💡 Hint

Think about where Cloud Shell stores your home directory and how it manages user files.

Cloud Shell provides a persistent home directory that is stored on a disk attached to your user account. This means files you create in your home directory remain available across sessions, even after hours or days.

❓ Configuration

intermediate

Setting the Default Project with gcloud CLI

You want to set your default project for gcloud commands to my-project-123. Which command will correctly set this default project?

A gcloud project set-default my-project-123

B gcloud config set project my-project-123

C gcloud config project set my-project-123

D gcloud set project my-project-123

💡 Hint

Remember the syntax for setting configuration properties in gcloud CLI.

The correct syntax to set the default project is gcloud config set project [PROJECT_ID]. This sets the project property in your active configuration.

❓ Architecture

advanced

Choosing the Right Environment for Long-Running Scripts

You need to run a script that will take 10 hours to complete. You want to use Cloud Shell or gcloud CLI. Which is the best approach to ensure the script runs without interruption?

A Use Cloud Shell to start a Compute Engine VM and run the script there to avoid session timeouts.

B Run the script directly in Cloud Shell; it will keep running even if you close the browser.

C Run the script in Cloud Shell and keep the browser tab open to prevent disconnection.

D Run the script using gcloud CLI on your local machine only.

💡 Hint

Consider Cloud Shell session limits and how to run long tasks reliably.

Cloud Shell sessions time out after a period of inactivity (usually 20 minutes). For long-running scripts, it's best to run them on a Compute Engine VM where you control the environment and uptime.

❓ security

advanced

Managing Credentials in Cloud Shell

You want to run gcloud commands in Cloud Shell that access multiple projects with different permissions. What is the best way to manage credentials securely?

A Use <code>gcloud auth login</code> multiple times to switch between accounts as needed.

B Use service account keys stored in Cloud Shell home directory for each project.

C Share your Cloud Shell session with others to use their credentials when needed.

D Use <code>gcloud config configurations</code> to create separate configurations for each project and account.

💡 Hint

Think about how gcloud CLI supports multiple configurations for different accounts and projects.

Using gcloud config configurations allows you to create and switch between multiple named configurations, each with its own credentials and settings. This is more secure and organized than storing keys or logging in repeatedly.

🧠 Conceptual

expert

Understanding Cloud Shell Resource Limits

Which of the following statements about Cloud Shell resource limits is TRUE?

A Cloud Shell sessions have a fixed 5 GB persistent home disk and 1.7 GB RAM with limited CPU.

B Cloud Shell automatically scales resources based on your script's demands.

C Cloud Shell provides unlimited CPU and memory resources for any workload.

D Cloud Shell allows running background processes indefinitely without session timeout.

💡 Hint

Recall the typical resource specifications and session behavior of Cloud Shell.

Cloud Shell provides a small VM with about 1.7 GB RAM, limited CPU, and a 5 GB persistent home directory. It is not designed for heavy workloads or unlimited resource use. Sessions also time out after inactivity.