READ Free Dumps For Microsoft- 70-533
| Question ID 13779 | You manage a cloud service on two instances. The service name is Service1 and the role
name is ServiceRole1.
Service1 has performance issues during heavy traffic periods.
You need to increase the existing deployment of Service1 to three instances.
Which Power Shell cmdlet should you use?
|
| Option A | PS C:\>Set-AzureService -ServiceName “Service1” -Label “ServiceRole1” -Description “Instance count=3”
|
| Option B | PS C:\>Set-AzureRole -ServiceName “Service1” -Slot “Production” -RoleName “ServiceRole1” -Count 3
|
| Option C | PS C:\>Add-AzureWebRole -Name “ServiceRole1” -Instances 3
|
| Option D | PS C:\> $instancecount = New-Object Hashtable$settings[INSTANCECOUNT=3] PS C:\> Set-AzureWebsite -AppSettings $instancecount ServiceRole1
|
| Correct Answer | B |
Explanation Explanation: The Set-AzureRole cmdlet sets the number of instances of a specified role to run in an Azure deployment Example This command sets the "MyTestRole3" role running in production on the "MySvc1" service to three instances. Windows PowerShell C:\PS>Set-AzureRole ServiceName "MySvc1" Slot "Production" RoleName "MyTestRole3" Count 3 References:
| Question ID 13780 | Your company network includes two branch offices. Users at the company access internal
virtual machines (VMs).
You want to ensure secure communications between the branch offices and the internal
VMs and network.
You need to create a site-to-site VPN connection.
What are two possible ways to achieve this goal? Each correct answer presents a
complete solution.
|
| Option A | a private IPv4 IP address and a compatible VPN device
|
| Option B | a private IPv4 IP address and a RRAS running on Windows Server 2012
|
| Option C | a public-facing IPv4 IP address and a compatible VPN device
|
| Option D | a public-facing IPv4 IP address and a RRAS running on Windows Server 2012
|
| Correct Answer | C,D |
Explanation Explanation: C (not A): VPN Device IP Address - This is public facing IPv4 address of your on-premises VPN device that youll use to connect to Azure. The VPN device cannot be located behind a NAT. D (Not B): At least one or preferably two publicly visible IP addresses: One of the IP addresses is used on the Windows Server 2012 machine that acts as the VPN device by using RRAS. The other optional IP address is to be used as the Default gateway for out- bound traffic from the on-premises network. If the second IP address is not available, it is possible to configure network address translation (NAT) on the RRAS machine itself, to be discussed in the following sections. It is important to note that the IP addresses must be public. They cannot be behind NAT and/or a firewall. References: