关于“通过内部负载均衡提高应用可靠性和可伸缩性”的评价

Kruti D R. · 已于 27 days前审核

Ana M. · 已于 27 days前审核

Ana M. · 已于 27 days前审核

keribeth l. · 已于 27 days前审核

Jorge F. · 已于 27 days前审核

The Documentation of this one has somethings missing

Gargi S. · 已于 27 days前审核

Load Balancing

Oscar Q. · 已于 27 days前审核

Harshita G. · 已于 27 days前审核

keribeth l. · 已于 27 days前审核

Jaime C. · 已于 27 days前审核

Víctor E. · 已于 27 days前审核

Sebastián S. · 已于 27 days前审核

Abid M. · 已于 27 days前审核

Amanda B. · 已于 27 days前审核

Have done all was at 90/100 couldn't submit for Enhance Application Reliability and Scalability with Internal Load Balancing even though all activties were done accurately.

Ananthu V. · 已于 27 days前审核

Siddharth B. · 已于 27 days前审核

Ananthu V. · 已于 27 days前审核

Siddharth B. · 已于 27 days前审核

Arelis R. · 已于 27 days前审核

Benjamin W. · 已于 27 days前审核

Arelis R. · 已于 27 days前审核

Itumeleng M. · 已于 27 days前审核

Jazmin C. · 已于 28 days前审核

MOHANAASRI G. · 已于 28 days前审核

Subject: Task 2 checker failure despite verified-correct configuration — Internal Load Balancer lab Hello, I'm working on the Internal Load Balancer lab (instance templates on subnet-a/subnet-b, network my-internal-app). Task 2's checker consistently returns the following error: "Please create the instance template on subnet-a subnetwork with the desired configuration." However, I have verified via `gcloud compute instance-templates describe instance-template-1` that the template is correctly configured: - machineType: e2-micro - subnetwork: subnet-a (region us-central1) - network: my-internal-app - tags: lb-backend - boot disk: debian-12 I have also confirmed: - Both backend instances are RUNNING and HEALTHY (backend-services get-health) - The Internal Load Balancer (10.10.30.5) correctly distributes traffic between instance-group-1 and instance-group-2 (verified via repeated curl tests from utility-vm) - Task 3 and Task 4 checks passed successfully I have attempted: - Recreating instance-template-1 from scratch (via a temporary template swap on the MIG) - A full lab restart The checker still fails on Task 2 with the same message. This appears to be a bug in the checker itself rather than a misconfiguration, as I've encountered this exact same issue on a separate lab as well (managed instance group task). Could you please investigate or manually award credit for this task? Project ID: qwiklabs-gcp-02-57f7af920d7f Lab: [insert lab name/ID here] Thank you.

Betta Z. · 已于 28 days前审核