1Z0-1067-25 Question 124
Single answerYou are investigating inconsistent memory consumption patterns on a fleet of OCI compute instances deployed across multiple availability domains. You want to retrieve the average MemoryUtilization metric over the last hour, grouping results by availability domain, while filtering only for resources of type 'compute_instance'. Which of the following MQL queries should you use?
- A
MemoryUtilization[1h]{resourceType = 'compute_instance'}.mean().groupBy('availabilityDomain')
- B
MemoryUtilization[1h]{resourceType = 'compute_instance'}.groupBy('availabilityDomain').mean()
- C
MemoryUtilization[1h].groupBy('availabilityDomain').mean()
- D
MemoryUtilization[1h]{availabilityDomain = 'compute_instance'}.groupBy('resourceType').mean()
Show answer and explanation
Correct answer: B
Explanation
In OCI Metric Query Language (MQL), you typically specify the metric name, time window, dimension filter, and then use the groupBy function followed by an aggregator (mean, max, sum, etc.). Option 2 follows the recommended structure for filtering by a dimension (resourceType = 'compute_instance'), grouping by availability domain, and then applying an aggregator. For more details, refer to the official Oracle Cloud Infrastructure Monitoring documentation on MQL syntax and usage.
- A. Incorrect.
Option 1: This form places the 'mean()' function before 'groupBy()', which typically results in an error. In OCI MQL, you generally apply groupBy first and then an aggregator function such as mean(), max(), or sum().
- B. Correct.
Option 2: This is the correct syntax. It filters the MemoryUtilization metric for 'resourceType = compute_instance', groups the results by 'availabilityDomain', and then calculates the average (mean) across the last hour time window.
- C. Incorrect.
Option 3: This query does group by availability domain and calculates the mean, but it does not filter for 'resourceType = compute_instance', so it would include all resources reporting MemoryUtilization, not just your compute instances.
- D. Incorrect.
Option 4: This query applies a dimension filter comparing 'availabilityDomain' to 'compute_instance', which does not make sense and would fail to capture the intended compute resources. It also mixes the dimension names incorrectly.