1Z0-531 · Question #14
You notice that your reports are running slower than before and realized that nothing in terms of data volume or dimension members has changed. You also checked the log file and found that no one…
The correct answer is A. Run a MaxL comment to see if the database is fragmented C. Check the data cache setting. A: Database fragmentation would slow down the database performance. You can use MaxL commands to check the fragmentation status. C: The data cache could affect the running time of the reports. Checking this cache would be a Incorrect answers Stop time of the application is not…
Question
You notice that your reports are running slower than before and realized that nothing in terms of data volume or dimension members has changed. You also checked the log file and found that no one ran any calculation. Which two would you look for to diagnose the cause of this slower response time?
Options
- ARun a MaxL comment to see if the database is fragmented
- BCheck when was the last time the application was stopped
- CCheck the data cache setting
- DCheck the commit-level setting
How the community answered
(60 responses)- A82% (49)
- B13% (8)
- D5% (3)
Explanation
A: Database fragmentation would slow down the database performance. You can use MaxL commands to check the fragmentation status. C: The data cache could affect the running time of the reports. Checking this cache would be a Incorrect answers Stop time of the application is not of interest here. The commit-level setting would affect real-time updates, not producing reports.
Topics
Community Discussion
No community discussion yet for this question.