Download Configuring and Operating a Hybrid Cloud with Microsoft Azure Stack.70-537.Pass4Sure.2019-07-24.49q.vcex

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

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 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. References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-replace-node

A user needs at least the reader role to be able to view resources in a tenant subscription.

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

When you create an offer, you must include at least one base plan, but you can also create add-on plans that users can add to their subscription. A subscription is how users access your offers. After you create an offer, users need a subscription to that offer before they can use it.  You can create subscriptions for both public and private offers. If do not want your tenants to create their own subscriptions, make all of your offers private, and then create subscriptions on behalf of your tenants. This approach is common when integrating Azure Stack with external billing or service catalog systems. After you create a subscription for a user, that user can log into the user portal and will find that they are subscribed to the offer.  Incorrect Answers:A: As the Azure Stack operator, you can delegate the creation of offers and users to other users by using the delegation functionality.C: The New-AzsOffer cmdlet creates an offer composing of the specified base plans and add-on plans.D: The Set-AzsSubscription cmdlet modifies the current logged-in user's tenant subscription.References:https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-delegated-provider https://docs.microsoft.com/en-za/powershell/module/azurerm.azurestackadmin/new-azsoffer?view=azurestackps-1.2.11https://docs.microsoft.com/en-za/powershell/module/azurerm.azurestackadmin/set-azssubscription?view=azurestackps-1.2.11https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-subscribe-plan-provision-vm

When you create you Linux VM via the portal or the CLI, you have two authentication choices. If you choose a password for SSH, Azure configures the VM to allow logins via passwords. If you chose to use an SSH public key, Azure configures the VM to only allow logins via SSH keys and disables password logins. To secure your Linux VM by only allowing SSH key logins, use the SSH public key option during the VM creation in the portal or CLI. References:https://docs.microsoft.com/en-us/azure/virtual-machines/linux/overview

The New-AzureRmRoleDefinition cmdlet creates a custom role in Azure Role-Based Access Control. Provide a role definition as an input to the command as a JSON file or a PSRoleDefinition object. Incorrect Answers:A: New-AzureRoleTemplate creates web and worker role templates.  This has nothing to do with RBAC.C: The permission definitions should be contained in a JSON file, not an XML file.D: New-AzureRoleTemplate creates web and worker role templates.  This has nothing to do with RBAC.References:https://docs.microsoft.com/en-us/powershell/module/azurerm.resources/new-azurermroledefinition?view=azurermps-6.2.0

References: https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-marketplace-publisher#publish-marketplace-items