Topic 1 Question 40
A data engineering team is using an Amazon Redshift data warehouse for operational reporting. The team wants to prevent performance issues that might result from long- running queries. A data engineer must choose a system table in Amazon Redshift to record anomalies when a query optimizer identifies conditions that might indicate performance issues. Which table views should the data engineer use to meet this requirement?
STL_USAGE_CONTROL
STL_ALERT_EVENT_LOG
STL_QUERY_METRICS
STL_PLAN_INFO
ユーザの投票
コメント(5)
B STL_ALERT_EVENT_LOG records any alerts/notifications related to queries or user-defined performance thresholds. This would capture optimizer alerts about potential performance issues.
STL_PLAN_INFO provides detailed info on execution plans. The optimizer statistics and warnings provide insight into problematic query plans.
STL_USAGE_CONTROL limits user activity but does not log anomalies.
STL_QUERY_METRICS has execution stats but no plan diagnostics.
By enabling alerts and checking STL_ALERT_EVENT_LOG and STL_PLAN_INFO, the data engineer can best detect and troubleshoot queries flagged by the optimizer as problematic before they impair performance. This meets the requirement to catch potential long running queries.
👍 5Felix_G2024/09/01- 正解だと思う選択肢: B👍 5GiorgioGss2024/09/18
- 正解だと思う選択肢: B
https://docs.aws.amazon.com/redshift/latest/dg/cm_chap_system-tables.html STL_ALERT_EVENT_LOG table view to meet this requirement. This system table in Amazon Redshift is designed to record anomalies when a query optimizer identifies conditions that might indicate performance issues
👍 1rralucard_2024/08/01
シャッフルモード