Your company has just launched a new critical revenue-generating web application. You deployed the application for scalability using managed instance groups, autoscaling, and a network load balancer…

Question

Options

• AUse Cloud Armor to blacklist the attacker's IP addresses.
• BIncrease the maximum autoscaling backend to accommodate the severe bursty traffic.
• CCreate a global HTTP(s) load balancer and move your application backend to this load balancer.
• DShut down the entire application in GCP for a few hours. The attack will stop when the application
• ESSH into the backend compute engine instances, and view the auth logs and syslogs to further

• A
  10% (4)
• B
  59% (23)
• C
  26% (10)
• D
  5% (2)

Explanation

The current setup uses a network load balancer, which does not support Cloud Armor (which requires an HTTP(S) load balancer). Therefore, option A is not immediately actionable without first completing option C, making C+A a multi-step migration rather than a quick fix. Option B (increase max autoscaling) immediately restores capacity so legitimate users can complete transactions, addressing the 'quickly restore access' requirement. Option E (SSH to view auth logs and syslogs) helps identify the attack source IPs and patterns, which is the next step toward building a targeted mitigation. Option D (shutting down the app) harms legitimate users. Together, B restores service quickly and E gathers the intelligence needed to address the root cause.

No community discussion yet for this question.