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:
Ref:
http://technet.microsoft.com/en-us/library/cc753442.aspx
http://technet.microsoft.com/en-us/library/cc772568.aspx
I think its ‘A’ as per the TechNet article in the explanation you will need to add the iSCSI targets during the discovery domain configuration thus ‘A’ 1st.
0
0
i think it is B correct
((To summarize, in order for an iSCSI target to be discovered by an iSCSI initiator, both must be members of the same Discovery Domain, and that Discovery Domain must be a member of an enabled Discovery Domain Set.))
http://technet.microsoft.com/en-us/library/cc753442.aspx
0
0
I am comfortable with Answer A.
Install Install iSCSI Target Server Role and Configure Targets.
Answer B, Install iSNS Server is for Initiators to AUTOMATICALLY Discover Targets.
(This is an answer for another question on the exam and good to remember)
Here is the same Question in another form.
Provide iSCSI Storage to a Server.
Your network contains three servers named Server1, Server2, and Server3.
All servers run Windows Server 2012.
You need to ensure that Server1 can provide iSCSI storage for Server2 and Server3.
What should you do on Server1?
A. Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties.
B. Install the iSNS Server service feature and create a Discovery Domain.
C. Install the Multipath I/O (MPIO) feature and configure the MPIO Properties.
D. Install the iSCSI Target Server role service and configure iSCSI targets.
Correct Answer: D
0
0
B
key is minimise admin effort:
in a large network, it’s much more manageable if you can find targets automatically.
iSNS Server is an installable Windows Server feature. iSNS acts as a central repository of iSCSI components that are available on a network.
iSNS generally works like this: First,you register iSCSI initiators and targets with the iSNS server. You then configure each iSCSI, Initiator with the address of the iSNS server. After that, initiators are able to query iSNS for a list of targets available on the network.
0
0
hah, you got the key right. When you have 50 drives you better have ISNS lol
0
0
I think the key here is that they are ’20 iSCSI storage appliances’. It doesn’t specify it being disks attached to another Windows server that would need the iSCSI Target role installed to get them started. It sounds like they are already set up as targets.
With that, I would go with B, iSNS Server service.
0
0
Correction to the above explanation.
After looking at the wording again. You are NOT Configuring the Storage\Target. You are Configuring the Host CONNECTION\Initiator to the Storage.
Answer:
Start the Microsoft iSCSI Initiator Service and Configure the iSCSI Initiator Properties.
—————————————————————————–
The ‘Alternative Question’ I posted above is to Configure the Storage\Target.
Microsoft is smooth with the wording.
1
0
From Pluralsight videos:
1. configure initiator
2. create storage on target
3. back to initiator to select the target and connect to it.
isns server service – provides a location for targets and initiators to register to. To be able to see registered iscsi initiator and targets in list.
Even if the targets are not connected, 2 places I read where the initiator must be configured first, before targets. (for some reason, my paste function is not working only on aiotestking. Google configuring iscsi storage Mitch Tulloch)
No where in the question does it say that the initiator has been created, no where does it say that the storage has been created as targets. I think that you are on the first step to create the storage, so I would go with
c. start the microsoft iscsi initiator service and configure iscsi initiator properties.
0
0
I agree with you
0
0
hmm on a second though “you need to configure the storage” makes me go for B
0
0
Yep. C.
You’re configuring the storage for the Hyper V hosts. Even if you decide to use iSNS, you still need to “start the initiator service and configure its properties”. You can’t have iSNS without active initiators!
1
0
Yes, you can – it’s just pretty useless without registered targets or initiators..
0
0
The order isn’t necessary to setup first the initiator, then the target! If you’re deploying a production environment, you have a solution designer or architect draft the entire network and storage fabric and assign static IPs for everything. So you could present the targets to the servers based not only on their IQNs, but also MAC addresses and IPs.
Regardless, in this case the correct answer should be C, yes.
0
0
c
“A software iSCSI initiator is installed by default on Windows Server 2012 and Hyper-V Server 2012 as the MSiSCSI service. However, the MSiSCSI service isn’t set to automatically startup, so we can start the MSiSCSI service with the following PowerShell command lines:
Set-Service –Name MSiSCSI –StartupType Automatic”
(http://blogs.technet.com/b/keithmayer/archive/2013/03/12/speaking-iscsi-with-windows-server-2012-and-hyper-v.aspx)
0
0
I believe it’s B
The wording of the question is key, it states “the solution must minimize administrative effort.” and “what should you do first”
The first thing to do if you wanted to make it easy is install iSNS.
0
1
wtf guys lol, doing this exam in 10 days. no idea on this one.
0
1
Ok thanks,
I was convinced of B. Now i’m not sure if it’s A,B,C or D.
2
0
The point of iSNS is automation in situations where… let’s say you have 20 iSCSI appliances. I have to believe some knowledge of iSNS is the point of the question.
There is another question with only two iSCSI servers, and in that question, the answer is not iSNS and with two targets – it’s not the least amount of effort.
0
0
This is a frustrating question. But I also have to go with C.
A is presumably wrong, because you already have iSCSI storage appliances that have already been configured as iSCSI Targets.
B is wrong only because the hosts have not been configured yet to “look” for targets. Before they can do that, the iSCSI initiator service hasn’t been started. Once it is started, iSNS is a prudent way to go.
D is just all the way wrong. There’s no need for multi-path I/O.
2
0
Its C 100%
0
0
I think the wording is very clever and might possibly lead many people down the wrong path as is shown in the discussion here so far
Read the wording carefully
Scenario is that you have 20 storage devices that will provide storage for 50
Hyper-V hosts and you need to configure the storage for the 50 Hyper-V hosts
IMO This indicates that no configuration has yet taken place
Many people will be looking at the current setup in the question but for minimal admin effort in the future…
Consider that each Hyper-V Host can have a maximum of 1024 Virtual Machines running
https://technet.microsoft.com/en-GB/library/jj680093.aspx
Would you like to manually configure each on of those iSCSI initiators to look for an iSCSI Target hosted on any one of your possible 20 storage devices ?
IMO The best solution is to install iSNS feature first.
You can then configure your targets and initiators to point at it for autodiscovery which will minimise future admin effort
https://technet.microsoft.com/en-gb/library/cc725692.aspx
After you have installed one or more iSNS servers, configure each iSCSI initiator and target in your SAN to use an iSNS server for discovery. This configuration is done in the configuration tools for initiators and targets, such as iSCSI Initiator in Control Panel.
I would go for B
1
1
I think A, do you not have to configure the targets before you can use them with the iSNS feature?
0
1
On second thoughts I think it is C. The official Microsoft process tells you to configure the initiator first, then go to the target and then back onto the initiator.
It can be done in any order but I would go with the order Microsoft advise.
1
1
My thinking is that you do not create a discovery domain until you have your initiators and targets? And CBT nuggets/Microsoft tell you to configure initiator before the target
0
1
Changed my mind, B sounds right.
Configure iSNS and then add all of the targets and initiators into the iSNS discovery domain
0
0
Except B says “Install the iSNS Server….” rather than “Configure iSNS…” – therefore your previous choice of C) is correct.
1
0
Its C 100% Microsoft exam experience
1
3
Yeah fuck you that means jack shit to anyone here.
3
1
Answer is A.
Windows server2012R2 includes an iSCSI Target role that, along with failover clustering, allows it to become a cost effective and high available iSCSI storage area. You can connect from our Hyper-v host to the iSCSI target on the storage array with the following PowerShell command line:
New-IscsiTargetPortal TargetPortalAddress
$target = Get-IscsiTarget
Connect-IscsiTarget NodeAddress $target.NodeAddress
Reference: Configure iSCSI Target Server Role on Windows Server 2012
0
1
Ok so let’s look at the question:
You need to configure the storage for the Hyper-V hosts. The solution must minimize
administrative effort.
So it wants to know what to do with the hosts that will connect to the storage appliances. Now, whether the storage appliance has been configured or not does not matter. What matter is what needs to be done to have the hosts connect to the appliance.
With that in mind, the correct answer would then be C.
Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties
0
0
I believe it’s B.
According to Technet (https://technet.microsoft.com/en-us/library/cc753442.aspx) :
It is possible to remove an iSCSI target from all Discovery Domains and manually configure an iSCSI initiator to access that target. This must be done outside of the context of an iSNS server and Discovery Domains, using the configuration tools for the initiator and the target, such as iSCSI Initiator in Control Panel.
Therefore, iSCSI Initiators and Targets are separate from iSNS. So in turn, iSNS will provide the least amount of effort.
2
1
B
0
0
It’s a very tricky question. Since everyone going for A, B & C, I will go with D. Remember, there must be a trick somewhere that made you believe its between ABC. So it must be D!
0
3
Jojo, good for you1 if you ever encounter the question in an exam i think you should defy them and choose answer E. 🙂
0
0
guys… minimize administrative effort for the job described, not the future administration. This takes out B.
reading the question tells me that nothing is configured yet so definitely should be A
0
0
I go for C, MS gives “storage appliance” which is likely a NAS server which would already be configured for iSCSI targets. iSNS is for iSCSI naming services like DNS for iSCSI and of which is NOT required for a simple iSCSI target connection. You simply need to connect to the iSCSI using the iSCSI Initioator and establish the connection.
B on the other hand isn’t specifically wrong, since there are x50 iSCSI clients it would be useful having a discovery domain but not required.
0
0
A is completely wrong
iSCSI Target Server role allows server to become a cost-effective and highly-available iSCSI Storage Array. You have 20 storage appliances already
B is the next step not the first one
C is correct
Microsoft iSCSI Initiator Service should be running on all servers then you can ( B ) set up ISNS to discover and connect targets and initiators.
1
0
This is another of the badly worded questions where you need to look at the general idea that MS is going for rather than analysing the grammar.
I think they key points here are, 20 “appliances” (this to me says 20 3rd party SANs, god know what you will do with all of those!), and the good old “minimize administrative effort”.
Now “configure the storage”, this is pretty vague, I think that this means “get the LUNs mapped to the servers” not “start the initiator service”.
If you agree that the questions is going after automating the mapping of the storage from these 20 SANs to the 50 servers then B is the answer.
0
0
Except you’re missing the key sentence “What should you do FIRST”. Whether or not B minimizes administrative effort is irrelevant, because that’s the second step, not the first step.
1
0
it IS the first step because first you set up the iSNS Discovery Server stuff, and then you configure the iSCSI appliances with this server’s IP address. 3rd step would then be to configure all the 50 HV hosts, and here comes the benefit because you give’em also just the iSNS IP, enabling auto discover/configure all of the 20 iSCSI targets…
0
0
you are right @netadmin, but i think they are looking for B
0
0
I agree that “Storage Appliance” = Already configured iScsi targets. So no need to add a server role.
MPIO makes no sense.
C is a lot of administrative effort.
I’m going with B.
0
0
It is A
0
3
ANSWER IS A
0
4
Before you can begin to configure shared storage, you need to start Microsoft iSCSI Initiator service and set it to start automatically in the future.
Exam-Ref. 70-412 ,128 CHAPTER 2 Configure file and storage solutions.
How could you be able to connect hosts to the target storages with iSNS haven’t started iSCSI initiator function yet?
1
0
The key is – DO FIRST, NOT minimize administrative effort!
0
0
Explanation of ExamCollection PREMIUM:
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
$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.
Reference: Configure iSCSI Target Server Role on Windows Server 2012
0
0
I think the answer is C “Start the Microsoft iSCSI Initiator Service and configure the iSCSI Initiator Properties”. The question saya “The solution must minimize administrative effort”
so if we first configure the initiator, later in identifying the Access Servers we do NOT need to manually type in the IQN of the initiator.
0
0
Forgot to mention, even if you type in the IQN value properly, some times you’ll end up facing problems in your network. So, the best way is to configure the initiator first.
0
0
I did my exam yesterday (passed with 876) and I had this question, despite my feeling I went for b and apparently it was the right choice, cause I got 100% on Configure and Manage High Availability, so it seems it’s the answer Microsoft is looking for!!
1
0
I am putting my faith in you… ive been researching this question for 30 minutes and i’ve given up. I am writing down B as the answer and going with it.
I hope you arent bullshitting us.
2
0
That’s great Fred. However, iSCSI isn’t in the “Configure and Manage High Availability” section. It’s in the “Configure File & Storage Solutions” section.
So what did you get for that?
0
0
and he didnt answer 🙂 I think under every question, there should be pool here.
0
0
Thanks a lot Halloween, I almost wanted to go for B because Fred has Misled Sahing here.
Fred must study deep or research before he can just bulls**ting us here…:)
0
0
Every the moment in a when we pick out blogs that we study. Listed below are the most current sites that we opt for.
0
0
Below youll obtain the link to some websites that we consider you ought to visit.
0
0
Wonderful story, reckoned we could combine some unrelated data, nevertheless genuinely really worth taking a appear, whoa did one find out about Mid East has got a lot more problerms at the same time
0
0
usually posts some quite fascinating stuff like this. If you are new to this site
0
0
just beneath, are several entirely not connected sites to ours, however, they are certainly worth going over
0
0
below youll come across the link to some sites that we believe you should visit
0
0
that is the finish of this write-up. Right here you will find some websites that we believe you will appreciate, just click the links over
0
0
we like to honor many other world wide web sites around the internet, even when they arent linked to us, by linking to them. Below are some webpages really worth checking out
0
0
usually posts some really interesting stuff like this. If youre new to this site
0
0
here are some links to internet sites that we link to simply because we assume they are worth visiting
0
0
we came across a cool web site that you may possibly appreciate. Take a appear in case you want
0
0
always a massive fan of linking to bloggers that I enjoy but do not get quite a bit of link like from
0
0
always a huge fan of linking to bloggers that I love but really don’t get a lot of link like from
0
0
one of our visitors not too long ago recommended the following website
0
0
the time to read or stop by the content or web pages we’ve linked to below the
0
0
Here is a superb Weblog You may Come across Intriguing that we Encourage You
0
0
although websites we backlink to below are considerably not connected to ours, we really feel they may be truly really worth a go as a result of, so have a look
0
0
please visit the web-sites we comply with, including this a single, as it represents our picks in the web
0
0
here are some links to web pages that we link to mainly because we believe they are really worth visiting
0
0
Every after inside a although we pick out blogs that we read. Listed beneath are the latest sites that we decide on
0
0
usually posts some very exciting stuff like this. If you are new to this site
0
0
please take a look at the sites we comply with, including this a single, because it represents our picks through the web
0
0
we came across a cool website which you may enjoy. Take a look if you want
0
0
usually posts some really interesting stuff like this. If youre new to this site
0
0
p.s.
Free 391q dumps from Google Drive:
https://drive.google.com/open?id=0B-ob6L_QjGLpfm94alk1eU9xWjFYRkVoNkl0cjRiOXZRRjVkUXNXTklicDdKZDJwRGJCM1k
0
0
here are some hyperlinks to sites that we link to mainly because we assume they may be really worth visiting
0
0
The details mentioned inside the post are some of the ideal accessible
0
0
one of our visitors recently encouraged the following website
0
0
please stop by the websites we follow, such as this one, as it represents our picks through the web
0
0
Elearningexams can surely be that one with an exclusive collection of Microsoft 70-412 exam dumps. Here each and every Microsoft 70-412 exam question is verified by industrial experts to deliver best quality study material for your definite success. Microsoft 70-412 exam dumps are present in both the PDF file and VCE. For more information and updated 70-412 exams study material please visit Elearningexams.
Source: http://www.elearningexams.com/70-412-dumps
0
0
Answer is A: This is from the book “In April 2011, the iSCSI Target was available to Windows Server 2008 R2 as a free down-load. Starting with Windows Server 2012, you can install the iSCSI Target Server role, so
that other Windows servers can provide iSCSI storage to other clients (including other Windows servers). After you install the iSCSI Target Server role, you use Server Manager to create the volumes that will be presented to clients and specify which servers can access the iSCSI LUNs. ” so after this you can install the iSNS to help you manage all the connections.
0
0
The trick here is to minimize administrative effort, so the correct answer is B, fuck! COME ON GUYS!
0
0