Mengembangkan Aplikasi Serverless di Cloud Run: Challenge Lab Ulasan

Revangga Brama Eka P. · Diulas 3 bulan lalu

Sargam G. · Diulas 3 bulan lalu

Joevian K. · Diulas 3 bulan lalu

Piyush D. · Diulas 3 bulan lalu

Divya J. · Diulas 3 bulan lalu

Manas M. · Diulas 3 bulan lalu

Phantom R. · Diulas 3 bulan lalu

Freddi D. · Diulas 3 bulan lalu

Shraddha B. · Diulas 3 bulan lalu

Rannia Herma P. · Diulas 3 bulan lalu

Lonard S. · Diulas 3 bulan lalu

Joe A. · Diulas 3 bulan lalu

Laila P. · Diulas 3 bulan lalu

Jin H. · Diulas 3 bulan lalu

Jin H. · Diulas 3 bulan lalu

Luis Felipe C. · Diulas 3 bulan lalu

Thabiso M. · Diulas 3 bulan lalu

The challenge lab contains several confusing and incorrect instructions. In Task 5, the command for retrieving the production Billing Service URL references private-billing-service-744, which belongs to the staging environment. It should reference the production service, billing-prod-service-834. Task 7 is also contradictory. The table specifies that the production frontend must be unauthenticated, but the assessment says to “Enable Authentication.” Based on the required architecture, the frontend should be publicly accessible while using its assigned service account to invoke the private Billing Service. These inconsistencies can cause learners to deploy or test the wrong Cloud Run service even when the architecture is configured correctly. The task instructions and validation commands should be updated to use the correct service names and clearly distinguish between public frontend access and authenticated service-to-service communication.

Roman H. · Diulas 3 bulan lalu

NAVEEN L. · Diulas 3 bulan lalu

Alexey P. · Diulas 3 bulan lalu

Dwi Gita A. · Diulas 3 bulan lalu

Shubhankar P. · Diulas 3 bulan lalu

Aleksandr G. · Diulas 3 bulan lalu

Pranav W. · Diulas 3 bulan lalu

Mohammed F. · Diulas 3 bulan lalu