Your company has deployed a new API to App Engine Standard environment. During testing, the API is not behaving as expected. You want to monitor the application over time to diagnose the problem within the application code without redeploying the application.
Which tool should you use?
To diagnose a problem in the application code without redeploying the application, the best tool is Stackdriver Debug Logpoints. This tool allows you to add log statements dynamically to your running application. These logpoints can help you log variable values and execution paths to understand what is happening within the application over time. Although it may not be for long-term monitoring, it is highly effective for troubleshooting specific code-related issues without the need for redeployment.
D is correct answer here.
D) is the answer as the api is not behaving as expected we have to put some logs in order to understand what is going one. So we can analyse logs on a period time. With C) is only one shot not over time.
D is correct
D can only be monitored for 24 hours. For long-term monitoring, Cloud Monitoring is the best choice. https://cloud.google.com/monitoring/docs/monitoring-overview?hl=ja#uptime-checks I vote for B.
If it requires just for testing purposes then option D because log points expire after 24 hours automatically, while monitoring keeps metrics for 6 weeks.
i think this question will become obsolete since Cloud debugger will be deprecated: Cloud Debugger is deprecated and will be shutdown May 31, 2023. See the deprecations page and release notes for more information. Cloud Debugger is deprecated and is scheduled for shutdown on May 31 2023. For an alternative, use the open source CLI tool, Snapshot Debugger. https://cloud.google.com/debugger/docs/release-notes In thi context i'll say D
Community choice is D
https://cloud.google.com/debugger/docs/using/logpoints
https://cloud.google.com/debugger/docs/using/logpoints
" You want to monitor the application over time to diagnose the problem within the application code" If it's only for moniroting it's B, but it mentions "within the code" so it should be D
But it says that you want to "monitor the application over time" first, not that you want to start debugging it already.
Stackdriver Debug Snapshots is a feature of Stackdriver Debugger that allows you to capture a snapshot of the state of your application at a specific point in time. This snapshot includes information about the variables and the call stack at the time the snapshot was taken, as well as any log output that was generated. To use Stackdriver Debug Snapshots to monitor your application, you would need to take periodic snapshots of your application and then analyze the snapshot data to identify any issues or problems. However, this would not be a real-time monitoring solution, and it would not allow you to continuously monitor your application for issues. Instead, it would be a way to investigate issues after they have occurred, by examining the state of the application at the time the snapshot was taken.
Stackdriver Debug Logpoints is a feature of Stackdriver Debugger that allows you to insert logging statements into your code without modifying or redeploying your application. This can be useful for troubleshooting issues with your application, as it allows you to output data to the log without having to modify your code and redeploy the application. To use Stackdriver Debug Logpoints to monitor your application, you would need to insert logpoints into your code at strategic points, and then analyze the log output to identify any issues or problems. However, this would not be a real-time monitoring solution, and it would not allow you to continuously monitor your application for issues. Instead, it would be a way to investigate issues after they have occurred, by examining the log output that was generated.
Answer is B: To monitor the application over time to diagnose a problem within the application code without redeploying the application, you should use Stackdriver Monitoring (B). Stackdriver Monitoring provides a range of tools that allow you to view and analyze performance metrics, traces, and logs for your application. This can help you identify and troubleshoot issues with your application.
D. Stackdriver Debug Logpoints
The Api required a monitoring tool, not troubleshooting
Option C: Stackdriver Debug Snapshots allow you to inspect the state of an application at any code location in production, without stopping or slowing down your applications.
You want to MONITOR the application - > Stackdriver MONITORING
https://www.exam-answer.com/which-tool-should-use-monitor-application-stackdriver-monitoring
You want to see what is the problem in the code without altering it. => Logpoints.
The best tool for this scenario is C. Stackdriver Debug Snapshots . Here's why: Stackdriver Debug Snapshots allow you to take a snapshot of your application's state at a specific point in time. This includes the call stack and variable values. This lets you examine the code's execution path and the values of variables at the time of the issue, helping you pinpoint the problem within the application code.
Here's why the other options are less suitable: A. Stackdriver Trace: Trace focuses on tracking the flow of requests through your application, providing insights into latency and performance bottlenecks. While helpful, it doesn't directly show you the state of variables within your code. B. Stackdriver Monitoring: Monitoring provides metrics and dashboards for overall application health and performance. It's great for identifying issues like high latency or errors, but it doesn't offer the granular code-level debugging that snapshots provide. D. Stackdriver Debug Logpoints: Logpoints allow you to add log statements to your application on the fly without redeploying. This is useful for adding debugging information, but it requires you to know where to add the log statements, which might not be obvious if you're unsure of the problem's location.