What is the likely consequence of backing up Qlik Sense without stopping services?

When backing up Qlik Sense without stopping the services, one of the primary risks is that applications and the repository may become out of sync. This is because the data being accessed and modified during the backup process can lead to inconsistencies. When services are running, users may be interacting with applications, making changes, and generating new data or sessions. Consequently, if a backup occurs during this activity, it may capture a partial state of apps that do not reflect the database correctly or might miss updates that are in progress.

By stopping services prior to a backup, you can ensure that no changes are occurring to the applications and data, leading to a more accurate and reliable backup. This is crucial for maintaining the integrity of the data and ensuring that the backup can be restored effectively, without the risk of retrieving a corrupted or inconsistent state.

Other options do not reflect the realities of how Qlik Sense backups function or the risks involved with performing them while services are active. Therefore, the consequence of backing up without stopping services directly relates to the potential for applications and the repository being out of sync.