Ans: B I don't find anything about ddos attacks and Cloud security Scanner & databases; its most used with App engine and compute so. I go with Stackdriver profiler

B - getting to know the app perf

option C

Ans: B I don't find anything about ddos attacks and Cloud security Scanner & databases; its most used with App engine and compute so.

C would be correct

I would go for B: As it says, "The **number** of concurrent active users remained stable." Since users report database timeout errors, the newly deployed version can only service a particular load and that load is **lower than** expected number. It is likely that the new version has changes that lead to high CPU utilization or any other bottleneck, so we should use the profiler to locate the issue.

B. Use Stackdriver Profiler to visualize the resources utilization throughout the application The most probable cause of the database timeout when the number of concurrent active users remained stable is a performance issue. Stackdriver Profiler can be used to identify and diagnose performance issues in the application. Profiler can help you to visualize the resources utilization throughout the application, including CPU and memory usage, and identify any parts of the application that might be causing high load. This can help you understand how the application is utilizing the resources and identify any bottlenecks in the code that might be causing the timeouts. Other possible solutions, while they can be useful in certain situations, are not as relevant in this scenario. Option A is not relevant as it is not related to the issue. Option C while it can be helpful in certain scenarios, in this case it's less likely to be the cause of the problem. Option D is a security tool that can detect vulnerabilities in the application, but it's not related to the database timeouts.

I would go for C. C. Determine whether there is an increased number of connections to the Cloud SQL instance. 1. Because users report the error message saying "database timeout". If the errors is from the application then it wouldn't be "database timeout", so rather than running Profiler in your application, go check whether there is an increased number of connections is more intuitive. 2. Other than that, the question mentions "After an update to the application" which imply that there could be a bug regarding to SQL so that's why if "concurrent active users remained stable", the database could still timeout because of bugs. Please be aware that "concurrent active users remained stable" doesn't mean qps (query-per-second) is still the same.

Ans: B Exam passed and taken on 19/12/2022, 50/50 from this dump without buying the full access and looking for 'devops' word here: https://www.examtopics.com/discussions/google/1/

Ans: B

Submit B

Answer B: Use Stackdriver Profiler to visualize the resources utilization throughout the application. High CPU usage can most definitely cause dropped or ignored connections. The database engine and underlying OS are fighting for resources and aren't able to respond to the connection in time. Finding out why the query is eating so much CPU usage and optimizing it. https://stackoverflow.com/questions/69919454/high-cpu-usage-on-cloud-sql-causing-timeouts # Cloud Profiler is a statistical, low-overhead profiler that continuously gathers CPU usage and memory-allocation information (supported profile types: CPU time, Heap, Allocated heap, Contention, Threads, Wall time) from your production applications. It attributes that information to the source code that generated it, helping you identify the parts of your application that are consuming the most resources, and otherwise illuminating your applications performance characteristics. https://cloud.google.com/profiler/docs/about-profiler

C as app update could have introduced a bug where although app user concurrency remain stable, could have introduced more db connections

Ans C is more feasible. If the user not changed but the devs forgot to close the unneeded connection can increase the connection count and produce this error.

B - Profiler allows you to see each specific process running in your application to find out bottle necks and resource intensive components

Cannot be A as it is Cloud SQL instance Cannot be D as problem started after a deployment To find out what is mentioned in C you will have to use Stack Driver, thus the answer should be B.

I will go with C, because when developers did the code change (nothing else changed), may be they have introduced a bug due to which the connection to the DB is increasing (DB connections need to be closed after use). DB connection is also something that should have an upper limit, otherwise, DB Read/Write will be badly affected. See the documentation for any DaaS, it has a limit on parallel connection