Topic 1 Question 190
You have a Compute Engine application that you want to autoscale when total memory usage exceeds 80%. You have installed the Cloud Monitoring agent and configured the autoscaling policy as follows: ✑ Metric identifier: agent.googleapis.com/memory/percent_used ✑ Filter: metric.label.state = 'used' ✑ Target utilization level: 80 ✑ Target type: GAUGE You observe that the application does not scale under high load. You want to resolve this. What should you do?
Change the Target type to DELTA_PER_MINUTE.
Change the Metric identifier to agent.googleapis.com/memory/bytes_used.
Change the filter to metric.label.state = 'used' AND metric.label.state = 'buffered' AND metric.label.state = 'cached' AND metric.label.state = 'slab'.
Change the filter to metric.label.state = 'free' and the Target utilization to 20.
ユーザの投票
コメント(17)
- 正解だと思う選択肢: C
C is correct answer: A. Change the Target type to DELTA_PER_MINUTE. (in this case the utlization tagret need to be in minutes which is not the case its percentage % and not time based. B. Change the Metric identifier to agent.googleapis.com/memory/bytes_used. (not applicable) C. Change the filter to metric.label.state = 'used' AND metric.label.state = 'buffered' AND metric.label.state = 'cached' AND metric.label.state = 'slab'. (this gives total memory used) D. Change the filter to metric.label.state = 'free' and the Target utilization to 20. (you would still need to change the the percent_used to percent_free)
https://cloud.google.com/compute/docs/autoscaler/scaling-cloud-monitoring-metrics
👍 20Mahmoud_E2022/10/20 - 正解だと思う選択肢: A
TARGET_TYPE: the value type for the metric. gauge: the autoscaler computes the average value of the data collected in the last couple of minutes and compares that to the utilization target. delta-per-minute: the autoscaler calculates the average rate of growth per minute and compares that to the utilization target. delta-per-second: the autoscaler calculates the average rate of growth per second and compares that to the utilization target. For accurate comparisons, if you set the utilization target in seconds, use delta-per-second as the target type. Likewise, use delta-per-minute for a utilization target in minutes.
👍 11kiappy812022/09/05 - 正解だと思う選択肢: D
The issue with the current configuration is that the autoscaling policy is based on the percentage of memory used, rather than the amount of free memory available. Therefore, even if the memory usage is high, the autoscaling policy may not trigger because the percentage of memory used is still below the target utilization level of 80%.
To fix this issue, you should change the filter to metric.label.state = 'free' and the target utilization to 20. This will cause the autoscaling policy to scale the application when the amount of free memory falls below 20%. This is the opposite of the current configuration, which scales the application when the percentage of memory used exceeds 80%.
👍 4omermahgoub2022/12/26
シャッフルモード