A DR site is a backup site that can be used to restore business operations in case of a disaster that affects the primary site. A warm site is a DR site that has some equipment and data ready to be activated quickly, but not as fast as a hot site that has fully operational systems and data. A cold site is a DR site that has only basic infrastructure and no equipment or data. The location of a DR site is an important factor to consider when designing and implementing a DR plan. A DR site that is too close to the primary site may be affected by the same disaster, such as a power outage, a flood, or an earthquake. A DR site that is too far away from the primary site may incur higher costs and latency issues. Therefore, a good practice is to set up a DR site that is geographically located in another region that has different risk factors and environmental conditions than the primary site. This can help ensure that the DR site is available and accessible when needed.

Social engineering and malware are external threats because they originate outside the company and can compromise security.

Check the performance log data: Reviewing performance logs will provide insights into what is causing the database to run slowly, such as high disk I/O, CPU bottlenecks, or network issues.
This is a logical next step to identify specific performance-related problems rather than jumping to solutions without understanding the root cause.

Role-based access control assigns permissions based on job roles, ensuring users are granted only the access necessary to perform their assigned duties.

System state: A system state backup includes essential system files, the registry, boot files, and other critical components required to restore an entire system. It is particularly useful for restoring a failed physical server to new hardware because it captures the configuration and settings needed for the operating system to function properly on the new machine.