Users across a enterprise mobile deployment report that a custom line-of-business application on their Android devices regularly freezes and stops responding during large background database synchronizations. Operating system performance monitoring indicates high memory usage tied to accumulated temporary sync files. A device restart resolves the sluggishness for only a few minutes before the sync process slows the app down again. The technician needs to resolve the performance degradation while strictly preserving the user's custom settings and local offline data files. Which of the following actions should the technician perform FIRST?
- Force stop the application and clear the application cache in the OS app settings menu.Answer
- BPerform a full factory reset of the mobile device and re-enroll it in the MDM platform.
- CClear the application data from the settings menu to reset app storage.
- DDownload the 64-bit Windows desktop installer for the application and run it in Android compatibility mode.
Answer
Force stopping the application and clearing its application cache from the Android settings menu is the correct first step.
Force stopping the app and clearing its cache is the proper least-invasive troubleshooting step for application freezing caused by temporary file bloat. Clearing the cache removes temporary transaction logs causing performance bottlenecks while preserving user account settings, offline databases, and application preferences.
Step-by-Step Solution
Key Concept
Least-Invasive Mobile App Performance Remediation (Cache vs. Data)
Estimated Time:2m 0s