Module 5: Storage in the Cloud

Looking for ‘Google Cloud Fundamentals: Core Infrastructure Module 5 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 5: Storage in the Cloud of Course 2: Google Cloud Fundamentals: Core Infrastructure – Preparing for Google Cloud Certification: Cloud Developer Professional Certificate

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Quiz - Storage in the Cloud

Graded Assignment

1. What is the correct use case for Cloud Storage?

  • Cloud Storage is well suited to providing the root file system of a Linux virtual machine.
  • Cloud Storage is well suited to providing durable and highly available object storage. ✅
  • Cloud Storage is well suited to providing data warehousing services.
  • Cloud Storage is well suited to providing RDBMS services.

Explanation:
Google Cloud Storage is an object storage service that offers high durability, availability, and scalability. It is designed for storing and retrieving unstructured data, such as images, videos, backups, and large datasets.

  • It isn’t meant for providing root file systems for virtual machines (that’s what Persistent Disks are for).
  • It isn’t a data warehousing solution (BigQuery is better for that).
  • It doesn’t support relational database management (Cloud SQL, Spanner, or Firestore are better suited for that).

2. Which relational database service can scale to higher database sizes?

  • Spanner ✅
  • Cloud SQL
  • Bigtable
  • Firestore

Explanation:
Cloud Spanner is a horizontally scalable, globally distributed relational database service that supports high availability, strong consistency, and massive scalability. It is designed for large-scale applications that require high transactional consistency.

  • Cloud SQL is a managed relational database but is not as scalable as Spanner.
  • Bigtable is a NoSQL database optimized for analytics, not relational data.
  • Firestore is a NoSQL document database for app development, not a relational database.

3. Why would a customer consider the Coldline storage class?

  • To save money on storing infrequently accessed data. ✅
  • To save money on storing frequently accessed data.
  • To improve security.
  • To use the Coldline Storage API.

Explanation:
Google Cloud Coldline Storage is designed for long-term storage of infrequently accessed data at a lower cost. It’s ideal for archival storage, backups, and disaster recovery.

  • If data needs to be accessed frequently, Standard Storage or Nearline Storage would be a better choice.
  • Coldline does not inherently improve security—security depends on IAM roles and encryption settings.
  • There is no separate Coldline Storage API—it uses the same Cloud Storage API as other storage classes.

Related contents:

Module 2: Introducing Google Cloud
Module 3: Resources and Access in the Cloud
Module 4: Virtual Machines and Networks in the Cloud
Module 6: Containers in the Cloud
Module 7: Applications in the Cloud
Module 8: Prompt Engineering

You might also like:

Course 3:

Leave a Reply