What is a drawback of the local database method of securing device access?

What is a drawback of the local database method of securing device access?

• A. It requires redundant network hardware
• B. User accounts must be configured on each device
• C. It does not support encrypted passwords
• D. It cannot be scaled for large networks

Answer: (B)

The local database method of securing device access indeed requires that user accounts be configured on each individual device. This means that, in a network with many devices, each device must be manually configured with the user accounts that are allowed to access it. Consequently, this can lead to increased administrative overhead, as any changes to user accounts must be propagated to every single device. If a user account needs to be added or modified, network administrators must make these changes on every device, which can be time-consuming and prone to errors. This localized approach to user account management can create consistency issues and complicate the process of user management in larger environments. For organizations with numerous routers, switches, or other devices, such a method becomes inefficient and may lead to security risks if some devices are not updated in a timely manner or if the same credentials are used across multiple devices. In larger networks, centralized authentication methods like RADIUS or TACACS+ are preferred as they streamline the management of user accounts and provide better scalability.

The local database method of securing device access indeed requires that user accounts be configured on each individual device. This means that, in a network with many devices, each device must be manually configured with the user accounts that are allowed to access it. Consequently, this can lead to increased administrative overhead, as any changes to user accounts must be propagated to every single device. If a user account needs to be added or modified, network administrators must make these changes on every device, which can be time-consuming and prone to errors.

This localized approach to user account management can create consistency issues and complicate the process of user management in larger environments. For organizations with numerous routers, switches, or other devices, such a method becomes inefficient and may lead to security risks if some devices are not updated in a timely manner or if the same credentials are used across multiple devices. In larger networks, centralized authentication methods like RADIUS or TACACS+ are preferred as they streamline the management of user accounts and provide better scalability.