Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Security Engineer Exam - Topic 4 Question 61 Discussion

A company has been running their application on Compute Engine. A bug in the application allowed a malicious user to repeatedly execute a script that results in the Compute Engine instance crashing. Although the bug has been fixed, you want to get notified in case this hack re-occurs.What should you do?
C) Log every execution of the script to Stackdriver Logging. Create a User-defined metric in Stackdriver Logging on the logs, and create a Stackdriver Dashboard displaying the metric.
A) Create an Alerting Policy in Stackdriver using a Process Health condition, checking that the number of executions of the script remains below the desired threshold. Enable notifications.
B) Create an Alerting Policy in Stackdriver using the CPU usage metric. Set the threshold to 80% to be notified when the CPU usage goes above this 80%.
D) Log every execution of the script to Stackdriver Logging. Configure BigQuery as a log sink, and create a BigQuery scheduled query to count the number of executions in a specific timeframe.

Google Professional Cloud Security Engineer Exam - Topic 4 Question 61 Discussion

Actual exam question for Google's Professional Cloud Security Engineer exam
Question #: 61
Topic #: 4
[All Professional Cloud Security Engineer Questions]

A company has been running their application on Compute Engine. A bug in the application allowed a malicious user to repeatedly execute a script that results in the Compute Engine instance crashing. Although the bug has been fixed, you want to get notified in case this hack re-occurs.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

VPC Flow Logs samples each VM's TCP, UDP, ICMP, ESP, and GRE flows. Both inbound and outbound flows are sampled. These flows can be between the VM and another VM, a host in your on-premises data center, a Google service, or a host on the internet. https://cloud.google.com/vpc/docs/flow-logs


by Tawna at Feb 25, 2023, 02:09 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Security Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dick
7 months ago
Wait, can a script really crash an entire instance? That's wild!
upvoted 0 times
...
Muriel
7 months ago
D sounds complicated, but it could give detailed insights.
upvoted 0 times
...
Emerson
7 months ago
C is interesting, but isn't it overkill for just tracking a single script?
upvoted 0 times
...
Sharee
8 months ago
I disagree, B is too generic. CPU spikes don't directly indicate the script issue.
upvoted 0 times
...
Lorrine
8 months ago
Option A seems like the best choice for monitoring specific script executions.
upvoted 0 times
...
Emiko
8 months ago
Option D seems like it could work too, especially with BigQuery for analysis, but I wonder if it's overkill for just monitoring script executions.
upvoted 0 times
...
Merrilee
8 months ago
I like option C because logging every execution seems like a good way to track the script, but I'm not sure how to set up the user-defined metric.
upvoted 0 times
...
Kimbery
8 months ago
I remember practicing with Stackdriver alerts, but I feel like using CPU usage like in option B might not directly address the script execution problem.
upvoted 0 times
...
Kimbery
8 months ago
I think option A sounds familiar, but I'm not entirely sure if a Process Health condition is the right way to go for this specific issue.
upvoted 0 times
...
Claribel
8 months ago
I'm a bit confused here. Wouldn't setting the cart to use a custom URL, option A, also help resolve the problem? That seems like a viable alternative to the Redis solution.
upvoted 0 times
...
Carlton
8 months ago
Okay, let me think this through. A reduction in reserves is bad, so it must be an "unfavorable development." And an increase is good, so it's an "advance development." I think I've got it!
upvoted 0 times
...
Joaquin
8 months ago
Hmm, this looks like a tricky one. I'll need to carefully read through the options and think about the context of the command output.
upvoted 0 times
...
Adria
1 year ago
I'm no expert, but Option C seems a bit overkill. Do I really need a Stackdriver Dashboard to track a simple script execution? Option A or D sound like the simpler and more effective solutions.
upvoted 0 times
Regenia
11 months ago
Yeah, Option D seems like a straightforward solution to keep track of the script executions.
upvoted 0 times
...
Tayna
12 months ago
Option D could also work well. Using BigQuery to count the executions could be efficient.
upvoted 0 times
...
Isadora
12 months ago
I agree, Option A seems like the most direct way to monitor the script executions.
upvoted 0 times
...
Whitley
1 year ago
Option A sounds like a good idea. It's important to be notified if the script is executed too many times.
upvoted 0 times
...
...
Amber
1 year ago
Option B? Really? Monitoring CPU usage to detect a script execution issue? That's like using a sledgehammer to kill a fly. Option A or D are the way to go here.
upvoted 0 times
...
Carlee
1 year ago
Haha, I bet the malicious user is just trying to crash the instance to get a day off work. Option A is definitely the way to go to keep an eye on that script.
upvoted 0 times
...
Alayna
1 year ago
I'd go with Option D. Logging the script executions to BigQuery and setting up a scheduled query to track the number of executions seems like a more robust and scalable solution.
upvoted 0 times
Leanora
12 months ago
True, but logging to BigQuery gives us more flexibility in analyzing the data and setting up custom queries.
upvoted 0 times
...
Quiana
12 months ago
But wouldn't it be easier to set up an Alerting Policy in Stackdriver to get notified if the hack re-occurs?
upvoted 0 times
...
Raylene
1 year ago
Option D sounds like a good idea. Storing the script executions in BigQuery can help us track the number of executions.
upvoted 0 times
...
...
Myrtie
1 year ago
Option A seems like the best choice here. Monitoring the process health and getting notified when the script executes more than the desired threshold is a proactive approach to detect and address the issue.
upvoted 0 times
Gail
11 months ago
D) Log every execution of the script to Stackdriver Logging. Configure BigQuery as a log sink, and create a BigQuery scheduled query to count the number of executions in a specific timeframe.
upvoted 0 times
...
Larae
12 months ago
A) That sounds like a good plan. Monitoring the process health will help catch any unusual activity.
upvoted 0 times
...
Lon
12 months ago
C) Log every execution of the script to Stackdriver Logging. Create a User-defined metric in Stackdriver Logging on the logs, and create a Stackdriver Dashboard displaying the metric.
upvoted 0 times
...
Carry
12 months ago
A) Create an Alerting Policy in Stackdriver using a Process Health condition, checking that the number of executions of the script remains below the desired threshold. Enable notifications.
upvoted 0 times
...
Sherman
12 months ago
C) Log every execution of the script to Stackdriver Logging. Create a User-defined metric in Stackdriver Logging on the logs, and create a Stackdriver Dashboard displaying the metric.
upvoted 0 times
...
Alyce
12 months ago
A) Definitely, being proactive in monitoring can help prevent any potential issues.
upvoted 0 times
...
Carissa
1 year ago
B) That sounds like a good idea. It's important to monitor the script executions to prevent crashes.
upvoted 0 times
...
Margot
1 year ago
A) Create an Alerting Policy in Stackdriver using a Process Health condition, checking that the number of executions of the script remains below the desired threshold. Enable notifications.
upvoted 0 times
...
...
Lilli
1 year ago
I'm not sure, but option C also sounds like a good idea. Logging every execution of the script could help us track any suspicious activity.
upvoted 0 times
...
Lavonna
1 year ago
I agree with Salina. Setting up an Alerting Policy with a Process Health condition seems like the most proactive approach.
upvoted 0 times
...
Salina
1 year ago
I think option A is the best choice. We need to monitor the script executions to prevent the hack from happening again.
upvoted 0 times
...

Save Cancel