Answer: Reentrante.

## Explanation This question is about operating system concepts related to device drivers. The scenario describes a device driver that can be interrupted while processing one task to handle another task from the same device. This is a classic characteristic of **reentrant code**. **Key Concepts:** 1. **Reentrant Code**: Code that can be safely interrupted and re-entered (called again) before the previous execution has completed. This is essential for device drivers that handle interrupts, as they must be able to handle new interrupts while still processing previous ones. 2. **Why other options are incorrect:** - **A) Assíncrono (Asynchronous)**: Refers to operations that don't block execution, but doesn't specifically describe the ability to be interrupted and re-entered. - **B) Assimétrico (Asymmetric)**: Typically refers to multiprocessing where processors have different roles, not relevant here. - **C) Elástico (Elastic)**: Usually refers to scalability or resource allocation, not code interruptibility. - **E) Recursivo (Recursive)**: Refers to functions that call themselves, which is different from being interruptible by external events. **Real-world application**: Device drivers in operating systems must be reentrant because hardware interrupts can occur at any time, and the driver must be able to handle new interrupts even while processing previous ones. This prevents data corruption and ensures system stability. **Correct Answer: D) Reentrante (Reentrant)**

Author: Danyel Barboza