File Info
| Exam | Configuring and Operating a Hybrid Cloud with Microsoft Azure Stack |
| Number | 70-537 |
| File Name | Microsoft.70-537.PrepDumps.2020-08-03.87q.vcex |
| Size | 3 MB |
| Posted | Aug 03, 2020 |
| Download | Microsoft.70-537.PrepDumps.2020-08-03.87q.vcex |
How to open VCEX & EXAM Files?
Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.
Coupon: MASTEREXAM
With discount: 20%
Demo Questions
Question 1
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.
You have an Azure Stack integrated system that runs in a connected environment.
You need to recommend an interval for installing Microsoft software update packages to Azure Stack. The solution must ensure that you can receive Microsoft support.
Solution: You recommend that Microsoft software updates be installed monthly.
Does this meet the goal?
- Yes
- No
Correct answer: A
Explanation:
For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions. Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month. Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months. References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policyhttps://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions.
Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month.
Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months.
References:
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policy
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates
Question 2
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.
You have an Azure Stack integrated system that runs in a connected environment.
You need to recommend an interval for installing Microsoft software update packages to Azure Stack. The solution must ensure that you can receive Microsoft support.
Solution: You recommend that Microsoft software updates be installed every six months.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions. Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month. Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months. References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policyhttps://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions.
Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month.
Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months.
References:
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policy
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates
Question 3
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.
You have an Azure Stack integrated system that runs in a connected environment.
You need to recommend an interval for installing Microsoft software update packages to Azure Stack. The solution must ensure that you can receive Microsoft support.
Solution: You recommend that Microsoft software updates be installed every 12 months.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions. Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month. Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months. References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policyhttps://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions.
Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month.
Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months.
References:
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policy
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates
Question 4
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.
You have an Azure Stack integrated system that runs in a connected environment.
You need to recommend an interval for installing Microsoft software update packages to Azure Stack. The solution must ensure that you can receive Microsoft support.
Solution: You recommend that Microsoft software updates be installed every three months.
Does this meet the goal?
- Yes
- No
Correct answer: A
Explanation:
For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions. Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month. Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months. References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policyhttps://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates For your Azure Stack deployment to remain in support, it must run the most recently released update version or run either of the two preceding update versions.
Microsoft will release update packages for Azure Stack integrated systems on a regular cadence that will typically fall on the fourth Tuesday of every month.
Thus to remain in support you must be running one of the last three update versions and, as an update version is released every month, you need to install updates at least every three months.
References:
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-servicing-policy
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-updates
Question 5
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.
You have an Azure Stack integrated system that contains four nodes named Node1, Node2, Node3 and Node4.
You plan to replace Node2.
You need to drain the active workloads that run on Node2.
Solution: From Node1, you run the Repair-AzsScaleUnitNode cmdlet.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit. To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet. Incorrect Answers:A: The Repair-AzsScaleUnitNode cmdlet repairs the node. It does not drain the node.References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit.
To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet.
Incorrect Answers:
A: The Repair-AzsScaleUnitNode cmdlet repairs the node. It does not drain the node.
References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node
Question 6
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.
You have an Azure Stack integrated system that contains four nodes named Node1, Node2, Node3 and Node4.
You plan to replace Node2.
You need to drain the active workloads that run on Node2.
Solution: From the hardware lifecycle host, you run the Stop-AzsScaleUnitNode cmdlet.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit. To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet. Incorrect Answers:A: The Stop-AzsScaleUnitNode cmdlet turns off the node. It’s the same as if you press the power button. It does not send a shutdown signal to the operating system. For planned power off operations, make sure you drain a scale unit node first. References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit.
To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet.
Incorrect Answers:
A: The Stop-AzsScaleUnitNode cmdlet turns off the node. It’s the same as if you press the power button. It does not send a shutdown signal to the operating system. For planned power off operations, make sure you drain a scale unit node first.
References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node
Question 7
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.
You have an Azure Stack integrated system that contains four nodes named Node1, Node2, Node3 and Node4.
You plan to replace Node2.
You need to drain the active workloads that run on Node2.
Solution: From the hardware lifecycle host, you run the Disable-AzsScaleUnitNode cmdlet.
Does this meet the goal?
- Yes
- No
Correct answer: A
Explanation:
The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit. To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet. References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit.
To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet.
References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node
Question 8
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.
You have an Azure Stack integrated system that contains four nodes named Node1, Node2, Node3 and Node4.
You plan to replace Node2.
You need to drain the active workloads that run on Node2.
Solution: You connect to the BMC web interface on Node2 and power off the node.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit. To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet. Incorrect Answers:A: The BMC web interface on Node2 can be used to power off the node. This does not send a shutdown signal to the operating system. For planned power off operations, make sure you drain a scale unit node first. References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node The Drain action evacuates all active workloads by distributing them among the remaining nodes in that particular scale unit.
To run the drain action through PowerShell, use the Disable-AzsScaleUnitNode cmdlet.
Incorrect Answers:
A: The BMC web interface on Node2 can be used to power off the node. This does not send a shutdown signal to the operating system. For planned power off operations, make sure you drain a scale unit node first.
References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node
Question 9
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.
You have an Azure Stack integrated system that uses a Microsoft Azure Active Directory (Azure AD) domain named contoso.com as the identify provider. The system has a tenant subscription that contains several resources.
In contoso.com, you can create a new user named User1.
User1 reports that when signed in to the Azure stack user portal, no resources are displayed.
You need to ensure that User1 can view the resources on the portal.
Solution: On the tenant subscription, you assign the Reader role to User1.
Does this meet the goal?
- Yes
- No
Correct answer: A
Explanation:
A user needs at least the reader role to be able to view resources in a tenant subscription. A user needs at least the reader role to be able to view resources in a tenant subscription.
Question 10
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.
You have an Azure Stack integrated system that uses a Microsoft Azure Active Directory (Azure AD) domain named contoso.com as the identify provider. The system has a tenant subscription that contains several resources.
In contoso.com, you can create a new user named User1.
User1 reports that when signed in to the Azure stack user portal, no resources are displayed.
You need to ensure that User1 can view the resources on the portal.
Solution: On the Default Provider Subscription, you assign a role to User1.
Does this meet the goal?
- Yes
- No
Correct answer: B
Explanation:
There are two portals in Azure Stack; the administrator portal and the user portal (sometimes referred to as the tenant portal.) The Default Provider Subscription is the administrator portal. The user needs to be assigned a role in the tenant (user) subscription, not the Default Provider (admin) subscription. References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-manage-portals There are two portals in Azure Stack; the administrator portal and the user portal (sometimes referred to as the tenant portal.)
The Default Provider Subscription is the administrator portal. The user needs to be assigned a role in the tenant (user) subscription, not the Default Provider (admin) subscription.
References:
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-manage-portals
