To solve this question, the user needs to have a basic understanding of access control and network security.
Option A: Can be done as it is an internal IP
This option is partially correct. Implementing access control based on a hard-coded IP address can be done for internal IPs, since they are less likely to change or conflict with other IPs on the network. However, this alone does not guarantee security, and other measures such as firewalls and intrusion detection systems should also be in place.
Option B: Can be done for internet-facing servers as there are no chances of IP conflicts
This option is incorrect. Even for internet-facing servers, there are chances of IP conflicts, especially if the server is part of a larger network. Relying solely on hard-coded IP addresses for access control is not a good security practice.
Option C: Is a good security practice
This option is incorrect. While hard-coding IP addresses for access control can be part of a larger security strategy, it is not a good practice to rely solely on this method. Attackers can spoof IP addresses or gain access to a trusted IP address through various means. A more comprehensive security approach is needed.
Option D: Is a bad security practice
This option is partially correct. Relying solely on hard-coded IP addresses for access control is not a good security practice, as it is vulnerable to spoofing and other attacks. However, this does not mean that the practice is completely bad. It can be used in conjunction with other security measures, but should not be the only method of access control.