Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your company uses a network ID of 10.0.0.0/8.
The company opens a new office that uses a network ID of 10.5.0.0/16. The office has three floors. Each floor has a VLAN. The network ID of each VLAN is 10.5.10.0/24, 10.5.20.0/24, and 10.5.30.0/24.
You create a distribution point for the new office.
You need to ensure that the clients in the new office obtain content from the new distribution point.
Solution: Create an IP address range boundary from 10.5.0.0/16.
Does this meet the goal?
A. Yes
B. No
I don’t see an example of supernet here.
https://books.google.pl/books?id=LQGWAAAAQBAJ&pg=PT260&lpg=PT260&dq=example+of+supernets+boundaries&source=bl&ots=TGCmfN1WDN&sig=ACfU3U1HaSIzkhiK98Vfhbzs9kNjahSkUA&hl=pl&sa=X&ved=2ahUKEwiO74uzybnkAhVE2KQKHdBYBz4Q6AEwFHoECAcQAQ#v=onepage&q=%2F24%20cidr%20number%20to%20%2F23&f=false
This question has a mistake and was confused with other question that ends like so “Solution: Create an Active Directory site associated to the 10.5.0.0/16 subnet, and then create an Active Directory site boundary.
Does this meet the goal?” answer should be (NO)
But the above question I believe is A. YES
-Network Discovery Enabled
-Create a Boundary Group with the adresses ranges of the new office
-Deploy the client for this boundary group
–Best Practice——-
Correct Answer should be B: 10.5.0.0/16 is used as supernet of the VLANS. Supernets are not supported.
…….
As noted at the beginning of this writing, SCCM does not support supernets. The examples above are intended to provide an understanding as to when use of supernets should and should not cause issues with site assignment/Client Push and package source location lookup. Hopefully this information assists in site design around and troubleshooting of such issues.
https://blogs.technet.microsoft.com/configurationmgr/2010/03/22/clarification-on-issues-resulting-from-the-use-of-supernets-in-configmgr-2007/
The range boundary would have to read 10.5.0.0 – 10.5.30.255 in order to include all the clients. Each subnet is subnetted as a /24 which would mean that each subnet would be 10.5.x0.0 – 10.5.x0.255
(of course each usable woudl only be .1-254 in the 4th octet.)
If this was done by subnet, then he would have to make 3 individuals boudaries and assign them to the one boundary group.
So basically the answer is correct. B
IP address range boundary from 10.5.0.0/16 – looks to be a correct answer.
A range includes a starting point, and an ending point. The above is incorrect because it only gives you subnet. It should look like this: IP range = 10.5.0.0 – 1.5.10.0
The question could be incorrect and meant to say subnet. Any one can confrim?