Learn to earn Bonus level lab 3 is working Properly now.

[harshit1921]

The problem is solved now, you can do the lab now, 
In order to complete the lab you need to run these 4 codes -
1

gcloud compute networks create vpc-cluster --bgp-routing-mode=regional --subnet-mode=custom
gcloud compute networks subnets create cluster --network=vpc-cluster --range=192.168.110.0/24 --region=us-central1 --enable-private-ip-google-access
gcloud compute networks create vpc-management --bgp-routing-mode=regional --subnet-mode=custom
gcloud compute networks subnets create management --network=vpc-management --range=192.168.120.0/24 --region=us-central1 --enable-private-ip-google-access
gcloud compute networks create vpc-prod --bgp-routing-mode=regional --subnet-mode=custom
gcloud compute networks subnets create prod --network=vpc-prod --range=10.0.0.0/24 --region=us-central1
gcloud compute networks create vpc-qa --bgp-routing-mode=regional --subnet-mode=custom
gcloud compute networks subnets create qa --network=vpc-qa --range=10.0.1.0/24 --region=us-central1
gcloud compute firewall-rules create ingress-qa --action allow --direction=INGRESS --source-ranges=0.0.0.0/0 --network=vpc-qa --rules all
gcloud compute firewall-rules create ingress-prod --action allow --direction=INGRESS --source-ranges=0.0.0.0/0 --network=vpc-prod --rules all
gcloud compute firewall-rules create rdp-management --action allow --direction=INGRESS --source-ranges=0.0.0.0/0 --network=vpc-management --rules tcp:3389

 2

gcloud compute instances create rdp-client --zone=us-central1-a  --machine-type=n1-standard-4 --image-project=qwiklabs-resources --image=sap-rdp-image --network=vpc-management --subnet=management --tags=rdp,http-server,https-server --boot-disk-type=pd-ssd

3

gcloud compute instances create linux-qa --zone us-central1-a --image-project=debian-cloud --image=debian-9-stretch-v20191210 --custom-cpu 1 --custom-memory 4 --network-interface subnet=qa,private-network-ip=10.0.1.4,no-address --metadata startup-script="\#! /bin/bash
useradd -m -p sa1trmaMoZ25A cp
EOF"

4

gcloud compute instances create linux-prod --zone us-central1-a --image-project=debian-cloud --image=debian-9-stretch-v20191210 --custom-cpu 1 --custom-memory 4 --network-interface subnet=prod,private-network-ip=10.0.0.4,no-address --metadata startup-script="\#! /bin/bash
useradd -m -p sa1trmaMoZ25A cp
EOF"

and now do the check my progress, you'll get green tick .

[Abhishek213]

what about The threat hunting and prevention one task ???

[harshit1921 · Accepted solution]

I Just checked , those parts have been removed from evaluation so no need to do those as of now , but later on when first 2 steps will work properly this lab can be done again and understood properly but for the sake of this game and deadline it has been removed from the evaluation.

[Abhishek213]

cool thanks for update

[saumya_prasad]

so what if the deployment is unsucessful?

[harshit1921]

If these two tasks give any error this means that you have not run first code properly  that i have provided above.

1. Configure Cluster Objects in SmartConsole
2. Deploy two Linux instances

rerun run the first command and then run rest of the codes and as rest of the tasks have been removed from the evaluation keeping the deadline in mind you don't need to do those

[saumya_prasad]

I am not getting this VM instance check-point-cloudguard-payg-1-vm as I am not creating the Check points because they are not getting deployed. Will it affect my further progress?

[harshit1921]

It didn't for me, but as this lab has bugs you may get error so the solution that  i have provided above can be used as a last resort. Just Start the lab run those 4 commands in shell and check the progress you'll get 100% progress . I have provided this solution as it will  help everybody  complete the bonus level and they won't face any error.

[Abhishek213]

Yeah try once

[Himanshu_rokde]

But the issue was never about that. The task asked to be using "Check Point CloudGuard IaaS Firewall & Threat Prevention", which was nowhere to be found on the GCP Marketplace. I did it with the "Check Point CloudGuard NGFW", I assumed NGFW to be short for Next Generation FireWall. And it worked. Though it has to be kept in mind that the High Availability one is BYOL, so the firewall has to PYAG.

[harshit1921]

Yes, i assumed the same thing and did the lab 4 times . i was successful  2 time and 2 times i was not successful . I understand that they changed names after 2020 as lab was last revised then but the problem didn't just stop at that , even if you followed all the steps with the name changed version still it gave error to some users that is why those checkmarks were removed from my point of view since Checkpoint  has changed the name of their product this whole lab should be deleted and a new one should be created with all the updated features. Yesterday  only i was checking same product on azure they have updated it there and hence it is easy to apply it there.