Update faq.adoc (#1585)

For docs bug: #1460

Added new content about HZC persistence features to the FAQs.

---------

Co-authored-by: James Holgate <130981049+JamesHazelcast@users.noreply.github.com>
Co-authored-by: Rob Swain <rob.swain@hazelcast.com>

Author: 3 people

docs/modules/ROOT/pages/faq.adoc

@@ -257,8 +257,15 @@ See the xref:management:cluster-utilities.adoc#enabling-lite-members[Lite Member
 '''
 **Does Hazelcast persist?**
 
-No. However, Hazelcast provides `MapStore` and `MapLoader` interfaces.
-For example, when you implement the `MapStore` interface, Hazelcast calls your store and load methods whenever needed.
+Yes. Hazelcast offers several optional mechanisms to persist data across restarts and failures:
+
+- Persistence: Hazelcast provides a Persistence feature that allows data to be persisted to disk. This feature can be enabled to save data for recovery after planned cluster shutdowns, unplanned single node failures, or unplanned cluster-wide failures.
+- MapStore and MapLoader: the MapStore and MapLoader interfaces allow you to implement custom persistence logic to store and load data from external systems.
+- File-based backups: Hazelcast offers features for backing up in-memory maps to files on local disk, persistent memory, or external databases. This includes the Persistence feature and MapStore.
+- Persistence for specific data structures: You can configure persistence for specific data structures like maps, job snapshots, and SQL metadata. This allows for data recovery in various scenarios including planned shutdowns and unplanned failures.
+- CP Subsystem Persistence: The CP Subsystem is designed to provide strong consistency and partition tolerance. This means that during network partitions, the system prioritizes consistency over availability, ensuring that all nodes have the most up-to-date and consistent data. The CP Persistence feature enhances the reliability of the CP Subsystem and ensures that the system can recover from failures without data loss.
+
+It's important to note that these persistence mechanisms are not enabled by default. Hazelcast focuses on in-memory operations for performance, with these persistence options available for scenarios where data durability across restarts or failures is required.
 
 '''
 **Can I use Hazelcast in a single server?**