Which two actions should a System Administrator take to ensure high availability in a Qlik Sense site?

Ensuring high availability in a Qlik Sense site involves creating a resilient architecture that can handle user requests without downtime. Configuring a network load balancer is crucial as it helps distribute incoming user traffic across multiple servers. This balanced distribution reduces the likelihood of overloading a single server and consequently minimizes the risk of outages, thereby enhancing user experience and maintaining continuous access to Qlik Sense.

Adding a rim node to the existing site complements this by allowing for additional processing capacity and redundancy. The rim node functions as a scale-out measure, enabling the site to manage more concurrent users and providing failover options if one component of the system becomes unavailable. Together, these actions work to create a more robust infrastructure that can serve users reliably, even during peak loads or when maintenance is required on primary nodes.

The other actions listed may contribute to an overall functioning system but do not specifically enhance high availability. For instance, increasing server capacity without a load balancer does not ensure that users have uninterrupted access. Scheduling reboots and updates is essential for maintenance but does not actively contribute to high availability when those procedures are taking place.