What of the following statements are true regarding /dev/ when using udev? (Choose TWO correct answers.)

udev is an event-driven system; it only creates device nodes for devices that are physically connected or virtually present and detected by the kernel, not for all possible devices beforehand.

Additional udev rules can be created and stored in /etc/udev/rules.d/ as .rules files; these custom rules allow administrators to define how udev manages specific devices, such as assigning persistent names or permissions.

Although udev automates device node creation, it is still technically possible to manually create block or character device files in /dev/ using the mknod command, though this is rarely needed for dynamically managed devices.

When using udev, the /dev directory is typically mounted as a tmpfs (a RAM-based filesystem) early in the boot process, and udev dynamically populates it with device nodes as hardware is detected and configured.

The content of /dev/ is generated dynamically at boot by udev and is not stored persistently in /etc/udev/dev (which is not a standard location) or restored from there.