PrepAway - Latest Free Exam Questions & Answers

Which PowerShell command should you use?

You administer an Azure subscription with an existing cloud service named
contosocloudservice. Contosocloudservice contains a set of related virtual machines (VMs)
named ContosoDC, ContosoSQL and ContosoWeb1.
You want to provision a new VM within contosocloudservice.

You need to use the latest gallery image to create a new Windows Server 2012 R2 VM that
has a target IOPS of 500 for any provisioned disks.
Which PowerShell command should you use?

PrepAway - Latest Free Exam Questions & Answers

A.
Option A

B.
Option B

C.
Option C

D.
Option D

Explanation:
http://msdn.microsoft.com/en-us/library/dn495159.aspx

26 Comments on “Which PowerShell command should you use?

  1. no pass says:

    no answer is correct.

    A. doesn’t stipulate a -servicename
    B. uses Basic_A1 which are at 300iops
    C. Doesn’t stipulate the latest gallery image
    D. Doesn’t include a provisioning config

    when run all of the scripts fail except B, which is using the wrong instance type.




    0



    0
  2. Tester says:

    I Select B as the correct

    After some testing, B is the only one that works. It has all the required parameters and the cloudservice already exists with the correct name. I tested it in the lab with Azure and it works, the VM gets created. No other works. They miss either the cloudservice or the adminname which are required.

    Thinking about it, it’s possible to provide disks to Windows with 600IOPS. This is Windows 2012 R2 !!! Attach 2 datadisks (2x300IOPS 2x1TB) Join them under StorageSpaces as striped set. Carve the required VHD and present them to Windows…
    http://blogs.technet.com/b/yungchou/archive/2012/08/31/windows-server-2012-storage-virtualization-explained.aspx




    1



    0
  3. Anon says:

    Does anyone actually read the questions????

    “that has a target IOPs of 500 for any provisioned disks”…that doesn’t mean you can add 2 disks and get 600 (300×2). They are obviously testing your knowledge of being able to understand the “standard tier” does 500 IOPs.




    0



    0
  4. Tester says:

    @Anon, while you correct on you observation you still miss the point. From the powershell cmdlets options presented only B works. Or either the options are incorrect or we are missing some information.




    0



    0
  5. cutedevil says:

    @Erwen is right,
    D is the answer -AdminUsername param is optional( Refer https://msdn.microsoft.com/en-us/library/azure/Dn495183.aspx)

    A cannot be the answer as the servicename is not passed in the command.

    New-AzureQuickVM cmdlet allows you to provision a single virtual machine with a simple configuration based on an image only

    Refer pg 63 of MS Examref 70-533 for detailed explanation of both the ways to create VM in Azure.

    Small is the correct size and i cannot find Basic_A1 in the list provided by MS might have changed the naming conventions

    (https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-size-specs/)




    0



    0
  6. Tony says:

    In my view, there are 3 possible answers, Option A, Option B and Option D. I believe Option C to be completely wrong.

    Now lets look at each option

    Option A. This script will not work without including the -ServiceName parameter

    Option B. This is the only command that is syntacally correct and runs. The question asks you to create a VM that has a target IOPS of 500 for any provisioned disks. The Basic_A1 creates a VM with 2 disks and a combined IOPS of 600. The question doesn’t mention IOPS per disk.

    Option D. This script will not work without including the -AdminUserName paramater

    So, in my view, B is the only possible answer




    1



    0
  7. RobV says:

    Confusing, but thinking D. Confirmed that -AdminUserName not required for New-AzureQuickVM.

    (B) does not meet IOPS requirement (Max IOPS per disk = 300) and requirement is target IOPS of 500 for any provisioned disks (i.e., ‘any’ meaning each??)

    Thoughts?




    0



    0
  8. Prady says:

    It should be D.

    Both B & D suffice for IOPS because both are stating the same VM instance type: Basic A1
    Small is Basic_A1 [ExtraSmall through ExtraLarge can also be named A0-A4 respectively: https://azure.microsoft.com/en-us/documentation/articles/cloud-services-sizes-specs/%5D

    Here’s the only catch I could find: Syntax for New-AzureVMConfig ‘s “-InstanceSize” parameter should be “Small” instead of “Basic_A1”.

    All in all, a very crappy question. Confusing candidates with two very similar cmdlets and with an optional component (-AdminUserName) which is impossible to guess unless you have used both cmdlets like a thousand times.
    New-AzureQuickVM creates and provisions a new VM. While New-AzureVMConfig only creates a VM Config Object, the options provide a full length working code making it so hard to differentiate… more so during an exam. We are having such a hard time even while looking up the documentation outside of the exam.
    Also, I don’t see what the big deal is in checking for that minor diff in Basic_A1 versus Small in the parameter name… I mean Basic_A1 was an accepted value until Microsoft decided to knock it off, still without an article stating it.




    0



    0
  9. snazzyrazmataz says:

    Found this explanation out in the wild…

    This is a hotly debated question. The syntax appears to be wrong in each choice.
    MS has been known to do this on purpose.
    When this occurs, your only choice is to choose the best option.

    In this case, we know that New-AzureVMConfig should be used as it fits the requirements of the question.
    http://msdn.microsoft.com/en-us/library/dn495159.aspx
    https://mohitgoyal.co/2016/09/26/configuration-options-available-in-new-azurequickvm-vs-new-azurevm/

    Also, we know that there is no “-InstanceSize” switch called “Basic_A1”, but there is one called “Small”
    https://docs.microsoft.com/en-us/azure/cloud-services/cloud-services-sizes-specs#a-series

    For this reason, we choose the option which uses New-AzureVMConfig and -InstanceSize Small.




    0



    0

Leave a Reply