Develop Serverless Applications on Cloud Run: Challenge Lab Reviews

Revangga Brama Eka P. · Reviewed 3 months ago

Sargam G. · Reviewed 3 months ago

Joevian K. · Reviewed 3 months ago

Piyush D. · Reviewed 3 months ago

Divya J. · Reviewed 3 months ago

Manas M. · Reviewed 3 months ago

Phantom R. · Reviewed 3 months ago

Freddi D. · Reviewed 3 months ago

Shraddha B. · Reviewed 3 months ago

Rannia Herma P. · Reviewed 3 months ago

Lonard S. · Reviewed 3 months ago

Joe A. · Reviewed 3 months ago

Laila P. · Reviewed 3 months ago

Jin H. · Reviewed 3 months ago

Jin H. · Reviewed 3 months ago

Luis Felipe C. · Reviewed 3 months ago

Thabiso M. · Reviewed 3 months 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 months ago

NAVEEN L. · Reviewed 3 months ago

Alexey P. · Reviewed 3 months ago

Dwi Gita A. · Reviewed 3 months ago

Shubhankar P. · Reviewed 3 months ago

Aleksandr G. · Reviewed 3 months ago

Pranav W. · Reviewed 3 months ago

Mohammed F. · Reviewed 3 months ago