Explain why a static mapping of names and IP addresses is impractical when the number of hosts is large.
What will be an ideal response?
If we have all IP addresses in /etc/hosts file, it is too complicated to maintain its integrity. If one host in a local area network changed its IP address, all hosts which have this IP address field for this machine in /etc/hosts should update their entry which is impractical for large networks. Similarly, when we only think of a mapping of fully qualified domain names and 32-bit IP addresses, it is impractical because domain name is given by the network classes. Class A which starts 0 in IP address is already almost consumed. For Class B which starts 10 in IP address is almost reaching its capacitance. Class C which starts 110 in IP address is available but the number of hosts in this network is only 256 which is small for an organization. These Class network address allocation has the problem and we are using CIDR subnetting network and routing by this scheme.
You might also like to view...
Computer forensics helps ________ in pre-search warrant preparations and post-seizure handling of computer equipment
Fill in the blank(s) with the appropriate word(s).
Which of the following is the version of func that is called?
Suppose we have a class D derived from base class B, ``` class B { public: // other members void func(); // other members }; void B::func() { /* body */} class D: public B { public: // other members void func(); // other members }; void D::func() { /* body */} D dObj; ``` Make the following call using dObj as calling object: dObj.func(); a)B::func() b) D::func() c) Neither d) Both e) This is illegal. The base class func() is inherited in the derived class. For this reason, it is illegal to have a function defined in a base class and in a derived class having the same signature.