Develop Serverless Applications on Cloud Run: Challenge Lab Reviews

Revangga Brama Eka P. · Reviewed 3 أشهر ago

Sargam G. · Reviewed 3 أشهر ago

Joevian K. · Reviewed 3 أشهر ago

Piyush D. · Reviewed 3 أشهر ago

Divya J. · Reviewed 3 أشهر ago

Manas M. · Reviewed 3 أشهر ago

Phantom R. · Reviewed 3 أشهر ago

Freddi D. · Reviewed 3 أشهر ago

Shraddha B. · Reviewed 3 أشهر ago

Rannia Herma P. · Reviewed 3 أشهر ago

Lonard S. · Reviewed 3 أشهر ago

Joe A. · Reviewed 3 أشهر ago

Laila P. · Reviewed 3 أشهر ago

Jin H. · Reviewed 3 أشهر ago

Jin H. · Reviewed 3 أشهر ago

Luis Felipe C. · Reviewed 3 أشهر ago

Thabiso M. · Reviewed 3 أشهر ago

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. · Reviewed 3 أشهر ago

NAVEEN L. · Reviewed 3 أشهر ago

Alexey P. · Reviewed 3 أشهر ago

Dwi Gita A. · Reviewed 3 أشهر ago

Shubhankar P. · Reviewed 3 أشهر ago

Aleksandr G. · Reviewed 3 أشهر ago

Pranav W. · Reviewed 3 أشهر ago

Mohammed F. · Reviewed 3 أشهر ago