Develop Serverless Applications on Cloud Run: Challenge Lab Reviews

Manas M. · Reviewed 3 месяцев ago

ok

Empires1 C. · Reviewed 3 месяцев ago

Kautsar A. · Reviewed 3 месяцев ago

Nabil H. · Reviewed 3 месяцев ago

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