Your network contains 20 iSCSI storage appliances that will provide storage for 50 Hyper-V hosts
running Windows Server 2012 R2.
You need to configure the storage for the Hyper-V hosts. The solution must minimize administrative
effort.
What should you do first?
A.
Install the iSCSI Target Server role service and configure iSCSI targets.
B.
Install the iSNS Server service feature and create a Discovery Domain.
C.
Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties.
D.
Install the Multipath I/O (MPIO) feature and configure the MPIO Properties.
Explanation:
Windows Server 2012 includes an iSCSI Target role that, along with Failover Clustering, allows it to
become a cost-effective and highly-available iSCSI Storage Array.
We can connect from our Hyper-V host to the iSCSI target on the storage array with the following
PowerShell command line:
New-IscsiTargetPortal –TargetPortalAddress<IP_Address or FQDN of storage array>
$target = Get-IscsiTarget
Connect-IscsiTarget –NodeAddress $target.NodeAddress
Incorrect:
Not B. Discovery Domains in an iSCSI fabric, like zones in a Fibre Channel fabric, enable you to
partition the storage resources in your storage area network (SAN). By creating and managing
Discovery Domains, you can control the iSCSI targets that each iSCSI initiator can see and log on to.
Configure iSCSI Target Server Role on Windows Server 2012
Its B iSNS
0
1
Ans: C
Ref: http://www.windowsnetworking.com/articles-tutorials/windows-server-2012/configuring-iscsi-storage-part2.html
0
1
Sorry Ans: A
Ref: http://www.mustbegeek.com/configure-iscsi-san-in-server-2012-r2/
1
0
A is wrong: 20 ISCSI storage appliances (with targets) are ready for provide the storage. Any other ISCSI target is useless.
B can be useful only after the configuration of ISCSI initiators.
So the first step is:
Exam Ref 70-412: Configuring Advanced Windows Server 2012 R2 Services
Page 128:
#Enabling iSCSI Initiator
The iSCSI client component included in Windows Server is called iSCSI Initiator. iSCSI Initiator is already installed by default, but its associated service (Microsoft iSCSI Initiator service) is not running by default. Before you can begin to configure shared storage, you need to start this service and set it to start automatically in the future.
Answer C: Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties.
2
0
To start already eliminated the letter D,
The question says “You need to configure the storage”, we eliminated the letter C.
Left A and B, the question says “effort minimum”. What it will help more in the process ??
So for me the letter B is correct.
0
0
Haha wow, this is the least helpful thread of all time. Thanks guys.
1
1
Yeah, and you’re bloody useless.
0
0
Exam passed (score 940)
2
0
p.s.
Free 391q dumps from Google Drive:
https://drive.google.com/open?id=0B-ob6L_QjGLpfm94alk1eU9xWjFYRkVoNkl0cjRiOXZRRjVkUXNXTklicDdKZDJwRGJCM1k
0
0
Thanks
0
0
Answer is C. iSNS
The Internet Storage Name Service (iSNS) protocol is used for interaction between iSNS servers and iSNS clients. iSNS clients are computers, also known as initiators, that are attempting to discover storage devices, also known as targets, on an Ethernet network. iSNS facilitates automated discovery, management, and configuration of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP network.
https://technet.microsoft.com/en-us/library/cc772568(v=ws.11).aspx
0
0
Surely in this instance the answer is A. The question states “20 ISCSI appliances that will provide storage”. There is no mention that these have been configured with targets on any given servers.
Therefore the first step is to set up the targets.
2nd step would be to set up ISNS.
Finally configure the initiators using the ISNS that was set up previously to make finding the targets easier.
0
0
hmmm, the question further asks about “You need to configure the storage for the Hyper-V hosts” and your first step “set up the targets” should be therefore done on the 20 iSCSI appliances as they will be acting as iSCSI targets for the Hyper-V hosts. Answer C is what you have to do on the Hyper-V hosts, and answer A and B could be the actions to perform on the storage appliances. But only if they are equipped with Windows Server OS, which would be a bit unusual IMHO…
so, this is just another f***ed up crappy Microsoft Question as the situation what exactly to do on which system under which cirumstances is quite unclear for me!
0
0
Surely in this case you have no friggin idea what you’re talking about: iscsi target role is for a 2012 server to provide local storage as iscsi targets. You CANNOT use it to setup external appliances like iSCSI SAN or NAS devices…
0
0
Ok, let’s wrap it up:
A – install iSCSI target provider role and setup targets is nonsense in the context of having 20 iSCSI storage appliances in the network. The target provider role lets you present local storage in form of storage spaces resources as iSCSI targets
D – MPIO is crucial performance-wise, but sometimes it causes issues whilst discovering new storage (especially in a boot-from-san scenarios, which is not the case, but important to know) because you see one target multiple times, this is why you first setup the storage and THEN setup mpio, once the discovery is setup properly.
C – iSNS let’s you monitor the discovery domains and targets/initiators, however you need to setup the initiators and targets first and then register them on the iSNS server, which obviously doesn’t help with the setup of the target in the first place
Which leaves us only with B – setup the initiators on the servers! The logical and practical way of setting an iSCSI environment goes like this: you need to setup the targets on the target providers (be it iSCSI storage, SAN with iSCSI interfaces, simply a 2012r2 instance with the iscsi target provider role or something else), then the initiators on the clients, then setup the LUN presentation and the discovery (be it static or dynamic) and THEN you can setup the iSNS and the MPIO.
So long story short – please stop replying to questions you have no clue about, simply because you’ve seen it in a dump somewhere! It doesn’t make you smart to learn by heart something wrong, especially if you haven’t done any of this stuff in a lab, let alone production environment. Furthermore you’re confusing less experienced people, who’d actually like to learn something…
0
0
sorry – I swapped the answers there: B is iSNS which is wrong and C is the initiators, which is right..
0
0
c
0
0
This is a no brainer for me! We have 20 targets and 50 initiators to handle! Here below are the advantages of iSNS…
Benefits of iSNS Server in iSCSI Storage Area Networks
• Centralized management
• Easily scalable to large IP storage networks
• Extensible
• Asynchronous notification of changes in the iSCSI storage network
• Ability to monitor the status and availability of clients
• Microsoft-preferred discovery method for iSCSI
• Designed for Windows Logo Program requirement for iSCSI HBAs
See this link…
https://technet.microsoft.com/en-us/library/cc772568(v=ws.11).aspx
Answer is clearly iSNS. Again, have people actually read the material, done the labs and watched the CBT / Pluralsight videos! Its drummed in from the word go exactly what the iSNS service is best at.
1
1