What are two reasons to deploy private addressing on a network? (Choose two.)
What are two reasons to deploy private addressing on a network? (Choose two.)
Private addressing serves two main purposes in a network. First, it segments local IP addresses from the global routing table, which helps to isolate internal network traffic from the global Internet, reducing the likelihood of IP address conflicts and providing a level of security for devices that do not need to be accessed from outside the local network. Second, it allows for the internal hiding of sensitive data from access within the enterprise. By using private IP addresses, sensitive internal resources are kept within the local network, which helps to protect them from unauthorized access both from within and outside the organization.
This bum ah question
A makes no sense as you could subnet public addresses into an organized hierarchy as well if you had reserved ipv4 addresses. As ipv4 addresses cost money it definitely will reduce the cost of maintaining your network.
yea that was weird man.. i could smell that bs from a mile away.
You can also argue if you need to subnet your public ip addresses, you are using a lot of them, which is not really cost effective... . You need to look at it from the enterprise perspective, they pay for a public IP or IP range from the ISP. The ISP will do the subnetting and will provide you with what you need if possible/available from their side (WAN) and if affordable for the enterprise. Enterprise does LAN subnetting, ISP manages WAN side i would say in most cases.
I don't think the ISP is going to subnet for a company because it wouldn't make sense to. If they needed to resize one of their subnets they would have to first contact the ISP? That doesn't seem logical nor practical when ISP are servicing hundreds or thousands of companies. It's more likely that the ISP would just allocate a range of IP addresses and let the companies have free reign over those IP addresses so the ISP wouldn't have to do anything when the companies reorganize their networks. But going back to your example you still had cost as a major decision factor.
can"t subnet an address when you have a limited address pool
make sense, this two options: public space cost money, private space none. You can't route private space to internet, but you can route to other private segment inside your organization (this vlan inter-routing as well). So i'm going with this two options.
Two reasons to deploy private addressing on a network are: A. to subnet addresses in an organized hierarchy: Private addressing allows an organization to create a structured and hierarchical network, making it easier to manage and allocate IP addresses efficiently within the internal network. C. to segment local IP addresses from the global routing table: Private addressing, such as the use of private IP address ranges (e.g., 192.168.x.x or 10.x.x.x), helps isolate internal network traffic from the global internet. This segmentation reduces the chances of IP address conflicts and helps maintain internal network privacy. Options B, D, and E do not directly relate to the deployment of private addressing for organizational networks. These options may have relevance in other network security or privacy contexts but are not specific reasons for deploying private addressing within an organization's internal network.
trash question
"to subnet addresses in an organized hierarchy" and "to hide sensitive data from access users within an enterprise" are common reasons for deploying private addressing on a network. Subnetting allows for better organization and management of IP addresses within a network, while private addressing can be used to protect sensitive data by limiting access to specific IP ranges.
AD, private ip addresses are easy to use and create highly organised network because you need the IANA approval and you're not limited on how much addresses you use. security because no one can access you're network from outside. the answer mention securtiy within a network it doesnt indicate where teh attack come from
BC is correct
Yesss. B AND C
chat gpt
its C&D
The answer to the question "What are two reasons to deploy private addressing on a network? (Choose two.)" is: A. to subnet addresses in an organized hierarchy D. to hide sensitive data from access users within an enterprise Private addressing is the use of IP addresses that are not globally routable over the Internet . The two common reasons for deploying private addressing on a network are to subnet addresses in an organized hierarchy and to hide sensitive data from access users within an enterprise . Using private addressing allows for efficient use of available IP address space and provides a level of security by keeping private IP addresses hidden from public view.
C. to segment local IP addresses from the global routing table D. to hide sensitive data from access users within an enterprise Explanation: C. Segmenting local IP addresses from the global routing table helps to improve network security by isolating internal network traffic from the public Internet and reducing the risk of unauthorized access. D. Hiding sensitive data from access users within an enterprise helps to maintain the confidentiality and security of confidential information, as internal private IP addresses are not publicly accessible. This helps to reduce the risk of unauthorized access to sensitive information by external parties.
A. to subnet addresses in an organized hierarchy is not a reason for deploying private addressing on a network because subnetting can be performed with either public or private IP addresses. The use of private addresses does not inherently provide a more organized hierarchy for subnetting IP addresses. The decision to use private addresses is typically driven by security and privacy considerations, rather than organizational considerations. B. to reduce network maintenance costs is not a reason for deploying private addressing on a network because deploying private addressing does not necessarily lead to cost savings for network maintenance. In fact, the use of private addresses can add complexity to network management and require additional resources for proper configuration and maintenance.
But the users data can be accessed by someone within the LAN
A+C . B > Public IPv4 addresses do cost more but that's not the reason we don't use them, there are very few addresses left . D. Private Addressing is not a valid security measure as specified by the CCNA curriculum E. wrong. Then in my opinion A+C is correct.
Ho ha senso
B & C are most correct
for me its A and D because its referred to ip private address main function
No, private addressing is not a valid security measure on its own. Although private IP addresses aren't routable on the Internet and are used to set up isolated internal networks, this doesn't actually protect against attacks.
Correct B and C. We think of the logic of IPv6 where public addresses (global unicast) have no cost to be used and we can create hierarchies of subnets with only public addresses. The question does not say which version of the IP, so we could use IPv6 for hierarchy with subnets of public addresses, but it would have a whole migration to IPv6 which could be unfeasible. In this case the letters "A" and "B" would not be the reasons for using private addresses, if this were the case with IPv6 referring to the cost. Now even with IPv6 having public addresses at no cost, we need to use a private address (unique-local unicast) in cases of confidentiality (security) of sensitive user information on an internal network, against external threats from the Internet in conjunction with a firewall, as security is always a determining factor for using a Unique Local, or even a range of private IPv4 addresses. However, it lacked information about the external network, leaving D half incorrect. (he follows...)
Now let's see the letter C, which describes the NAT process (PAT) of the inside global table that with just one (or more) public IPs we can already segment to several inside local addresses (private IPs) in the internal network. Because the answer to the letter C is correct for IPv4 use, I believe that the question is about IPv4 and not IPv6, so reducing maintenance costs for public IPs would make sense in IPv4, public IPv4 addresses have significant costs in an "end-to-end" user project, and this awareness is necessary, so I choose letter B. "to reduce network maintenance costs" and letter C. "to segment local IP from the global".
"Global routing table" , in Cisco documentation at least, does not refer to some routing table of the whole Internet, it seems to refer to the routing table on a router that contains routes from different sources. Someone knowledgeable please correct me if I'm wrong, otherwise, segmenting private IP addresses from the global routing table makes no sense and therefore it can't be C. Cisco is trying to trick us with that one! Absolutely using private addressing saves money!!! Companies have to pay their ISP for public address space, what companies choose to do with the address space is up to them to subnet but they have to buy the space from their ISP just the same.