Create and Manage Cloud Storage Buckets and Encryption Reviews

Romina Q. · Reviewed 15 days ago

the below instructed commands not working: " gsutil kms encryption -d gs://$BUCKET_NAME_1/ gcloud storage cp setup2.html gs://$BUCKET_NAME_1/ gcloud storage cp setup3.html gs://$BUCKET_NAME_1/ " and couldn't pass through "check progress" very disappointed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Michael L. · Reviewed 15 days ago

Jairo H. · Reviewed 15 days ago

Alberto L. · Reviewed 15 days ago

Jose M. · Reviewed 15 days ago

Piotr K. · Reviewed 15 days ago

Pradeep S. · Reviewed 15 days ago

Could not get this section to show completed, but was able to complete the steps.

Monica H. · Reviewed 15 days ago

Till H. · Reviewed 15 days ago

The lab is not functioning correctly. I had created the bucket with the correct specification and uploaded the files with the CSEK and the CSEK progress step did not complete. I verified that the files were marked as CSEK in the encryption column.

Alejandro C. · Reviewed 15 days ago

Dustin J. · Reviewed 15 days ago

DHESIKAN DR S. · Reviewed 15 days ago

Олександр Ш. · Reviewed 15 days ago

Geetika P. · Reviewed 15 days ago

Pradeep S. · Reviewed 15 days ago

Ariel Marcelo S. · Reviewed 15 days ago

Lab Defect Report: Task 3 (CSEK) is structurally broken due to incomplete CLI migration. The assessment for the Customer-Supplied Encryption Keys (CSEK) task is impossible to pass due to a fundamental desynchronization between the lab instructions, the grading script, and the current behavior of the Google Cloud SDK. CLI Conflict: The lab instructs users to configure the CSEK in the .boto file (legacy gsutil behavior) but mandates uploading the objects using the modern gcloud storage cp command. The modern gcloud storage CLI ignores .boto encryption configurations entirely. Silent Failures: Following the lab instructions results in objects being uploaded without encryption. Querying the API (gcloud storage objects describe --format="json(customerEncryption)") returns null. The validation script then correctly detects the lack of encryption and fails the student. Broken Cloud Shell Environment: Attempting to force the encryption by passing the key directly via the --encryption-key flag or modifying core SDK variables (CLOUDSDK_STORAGE_ENCRYPTION_KEY) in the provided Cloud Shell also fails silently. The underlying cryptographic libraries in this specific ephemeral environment appear to be desynchronized or restricted. The lab needs an immediate architectural update to either fully embrace the modern gcloud storage encryption parameters or revert to gsutil for both configuration and execution. The current state wastes students' time on an unsolvable technical bottleneck. Additional comments from Gemini El diagnóstico crudo y directo: el null en la telemetría es la prueba irrefutable de que tus archivos jamás fueron encriptados. El fracaso no ha sido tuyo; el laboratorio de Google está roto desde su diseño operativo. Aquí está el punto ciego técnico que ni tú ni el evaluador de Qwiklabs vieron: Google está forzando una migración de herramientas (de gsutil a gcloud storage). Los creadores del laboratorio actualizaron las instrucciones a medias. Te exigen configurar la llave en el archivo .boto (que solo lee la herramienta vieja), pero luego te ordenan subir los archivos con gcloud storage cp (la herramienta nueva, que ignora por completo el archivo .boto).

Carlos A. · Reviewed 15 days ago

Antonella L. · Reviewed 15 days ago

Sergio Matias D. · Reviewed 15 days ago

Rajesh G. · Reviewed 15 days ago

Struggling with CESK section where after uploading files with CESK enxryption still the task is not getting completed and saying 'Please create Cloud Storage bucket and upload files in bucket using Customer-supplied encryption keys.

Akshay J. · Reviewed 15 days ago

Nishant Kumar P. · Reviewed 15 days ago

Sharun S. · Reviewed 15 days ago

I'm not getting the encryption part to be approved even though I'm doing what the instruction says

Andreas v. · Reviewed 15 days ago

CSEK check doesn't work and completing without that check doesn't result in a complete

Miguel Filipe M. · Reviewed 15 days ago