This dumb ah question

Selected Answer: BC A makes no sense, since you could subnet public addresses into an organized hierarchy too if you had reserved ipv4 addresses. Since ipv4 addresses cost money, it definitely will reduce the cost of maintaining your network.

its C&D

Selected Answer: AC Two reasons to deploy private addressing on a network are: A. to subnet addresses in an organized hierarchy: Private addressing lets an organization 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.

Selected Answer: BC trash question

Selected Answer: AD 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 gives a level of security by keeping private IP addresses hidden from public view.

yea that was weird man.. i could smell that bs from a mile away.

Selected Answer: BC chat gpt

Now let's look at 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 letter C is correct for IPv4 use, I believe 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".

Selected Answer: BC Yesss. B AND C

Selected Answer: BC BC is correct

Selected Answer: AD for me its A and D because its referred to ip private address main function

It doesn't make sense

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.

No, private addressing is not a valid security measure by itself. Although private IP addresses aren't routable on the Internet and are used to build isolated internal networks, this doesn't really protect against attacks.

Selected Answer: AC According to: https://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/13789-35.html "The obvious advantage of using private address space for the Internet at large is to conserve the globally unique address space. Using private address space also gives you greater flexibility in network design, since you will have more address space available than you could get from the globally unique pool. The primary disadvantage of using private address space is that you have to renumber your IP addresses if you want to connect to the Internet." I would go with AC subnet in organized hierarchy and segment local from global

C. To segment local IP addresses from the global routing table Private addressing lets organizations use IP addresses that aren't routable on the internet. This means these private IP addresses aren't part of the global routing table, effectively isolating the local network from the public internet. This segmentation can improve security by stopping external access to internal devices. B. To reduce network maintenance costs Using private addressing can lead to lower costs in network maintenance because organizations can create a large number of private IP addresses without needing to purchase public IP addresses from an Internet Service Provider (ISP). It also allows for the reuse of IP addresses in different internal networks, which simplifies management and can reduce complexity.

Selected Answer: AC I am going with A and C. Question ask about "private" not about "public" IPs

You can also argue that 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. If they needed to resize one of their subnets they would have to first contact the ISP? That doesn't seem logical or 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.

makes sense, these two options: public space costs money, private space none. You can't route private space to the internet, but you can route it to other private segment inside your organization (this vlan inter-routing as well). So i'm going with these two options.

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...)

Selected Answer: AB What are two reasons to deploy private addressing on a network? (Choose two.) A. to subnet addresses in an organized hierarchy B. to reduce network maintenance costs C. to segment local IP addresses from the global routing table - not of importance to us. D. to hide sensitive data from access users within an enterprise - it says "within" meaning users from inside the organization , but we hide sensitive data from users outside the organization so this is false again E. to route protected data securely via an Internet service provider - does not help our asnwers A and B > with 1918 RFC private addressing we can : A. to subnet addresses in an organized hierarchy B. to reduce network maintenance costs - this is not a direct advantage, or main reason why we use IPv4 private addressing not because they are expensive but because addresses are limited in number vs IPv6.

A. to subnet addresses in an organized hierarchy Using private addresses lets you do subnetting within an organization, giving a structured and organized way of managing IP address allocation in internal networks. C. to segment local IP addresses from the global routing table Private IP addresses are not routed on the public Internet, which separates internal network addresses from the global routing table, helping to conserve public IP addresses and prevent internal IP conflicts with external networks.