What will occur if a backup of Qlik Sense is performed without stopping services?

When a backup of Qlik Sense is performed without stopping services, the most significant concern is that the backup of apps from the shared folder may become corrupted. This is primarily because, during active usage, data may be in a dynamic state as users interact with the system. If changes are being made to the apps or data when the backup occurs, there's a high likelihood that those intermediate states may not be captured correctly, leading to inconsistencies or corrupt files once the backup is complete.

Proper backup procedures typically require the suspension of services to ensure data consistency and integrity. Stopping the services allows for a point-in-time capture of the state of the applications and their associated data without any ongoing transactions or modifications, which is crucial for restoring functionality if needed.

The other outcomes mentioned in the choices are less relevant in this context. While it's possible that a backup may be incomplete or not created at all if interruptions occur, the primary issue with backing up during active use pertains to the potential corruption of existing app data. Hence, focusing on the integrity of the apps in the shared folder naturally leads to the conclusion that corruption is a significant risk when services are not halted during the backup process.