The Performance Monitoring Infrastructure collects counters from server components, and it is designed to cause as little overhead as possible. To that end, updates to the three basic statistic types, CountStatistic, AverageStatistic, and TimeStatistic, are not synchronised by default. Without synchronisation, two threads that update the same counter at once might overwrite each other, so the reported values can be slightly inaccurate, but the cost of locking is avoided. Where accuracy matters more than overhead, the administrator can turn on synchronisation for every statistic type. In the administrative console, this is done in the PMI settings for the server by selecting the Use sequential update check box. Option C is correct.
The other approaches do not alter how counters are updated. Writing a JMX client, option A, changes how the data is retrieved and leaves the collection untouched. The Custom option, option B, selects which counters are enabled, and the All option, option D, enables every counter in the set; both govern the volume of data and are unrelated to update synchronisation. Enabling all counters would, in fact, increase the overhead.
Because sequential update increases the cost of monitoring, it should be applied only when slight inaccuracies are unacceptable. In most tuning exercises the default's accuracy is adequate, since trends rather than exact values drive decisions.
[Reference: Performance Monitoring Infrastructure (PMI); Enabling PMI and statistic sets; Use sequential update setting.]