Cloud Storage Rezensionen

Francisco F. · Vor 8 Tage überprüft

Rabah G. · Vor 8 Tage überprüft

HEMANTH S S. · Vor 8 Tage überprüft

HEMANTH S S. · Vor 8 Tage überprüft

JAMES M S. · Vor 8 Tage überprüft

Part about encryption is not working correctly. Tried different ways of changing that and even was able to achieve customer-supplied encryption instead of google-managed, but couldn't successfully pass the checkpoint.

Krzysztof K. · Vor 8 Tage überprüft

Issue Description: The "Check my Progress" button for Task 3 (Customer-supplied encryption keys) is broken and does not award the 20 points, even when files are successfully customer-encrypted. Technical Root Cause: The lab instructions provide a mix of two different CLI tools for the encryption sequence: gsutil kms encryption -d gs://$BUCKET_NAME_1 gcloud storage cp setup2.html gs://$BUCKET_NAME_1/ Because gcloud storage completely ignores the ~/.boto configuration file where the encryption key is stored, these commands upload the files using standard Google-managed encryption instead of Customer-supplied encryption (CSEK). When I manually patched this by forcing the encryption via explicit flags, the files became properly customer-encrypted in the console. However, the automated "Check my Progress" script still failed to recognize it and denied the 20 points, likely because it strictly looks for a command history or metadata state generated only by the broken default commands. Suggested Fix: Update the validation script and the lab instructions to use one consistent CLI tool (either entirely gsutil or entirely gcloud storage) so that the progress check works and students receive their points.

Marina B. · Vor 8 Tage überprüft

not working Customer-supplied encryption keys.

Andrii H. · Vor 8 Tage überprüft

No task 3 was completly broken

Salvador Basso C. · Vor 8 Tage überprüft

The lab checker for Task 3 (CSEK) is completely broken. I successfully uploaded setup2.html and setup3.html with AES-256 customer-supplied encryption keys, verified with gsutil stat showing Encryption algorithm: AES256 on both files, yet the checker kept returning 0 points. I spent my entire lab session on this single task due to two undocumented issues: (1) the instructions tell you to run gsutil kms encryption -d which silently breaks CSEK uploads, and (2) newly created buckets have an org-level policy restricting CSEK that is never mentioned anywhere. The lab needs a full rewrite. Extremely frustrating experience.

Firmin T. · Vor 8 Tage überprüft

Aunque completado el paso 3, no me lo reconoce como hecho

David S. · Vor 8 Tage überprüft

Poor lab - commands do not work properly

Nizar M. · Vor 8 Tage überprüft

jennifer m. · Vor 8 Tage überprüft

cool

Varsha Sagar K. · Vor 8 Tage überprüft

Absolute garbage, every time. A waste of my life. Every time.

Dustin J. · Vor 8 Tage überprüft

Praveen S. · Vor 8 Tage überprüft

even after completing the task 3 and checking and doing everything as required it is saying 0/20 the grader is stuck

Riya M. · Vor 8 Tage überprüft

bramasakthi h. · Vor 8 Tage überprüft

Fernando J. · Vor 8 Tage überprüft

good

Nandika R. · Vor 8 Tage überprüft

Saloni K. · Vor 8 Tage überprüft

K SHRINIDHI S. · Vor 9 Tage überprüft

validation of CSEK part is not working

céline d. · Vor 9 Tage überprüft

HEMANTH S S. · Vor 9 Tage überprüft

Naman Goyal 2. · Vor 9 Tage überprüft