Tutorial / Cram Notes
Before initiating an Azure Stack Hub deployment, it is crucial to organize the required files into a logical folder hierarchy. Typically, you will need a directory for the Azure Stack Hub deployment package and another for certificate files. For instance:
AzureStackDeployment
│
├───Binaries
│ ├───AzureStackInstaller
│ └───SupportingFiles
├───Certificates
│ ├───AzureStackCertificate.pfx
│ └───CertificateSigningRequest.csr
└───Config
└───ConfigFile.json
In the Binaries folder, you would store the actual deployment binaries such as the installer and any additional files required during installation. The Certificates folder would contain all necessary certificates, including the .pfx file for secure communications and a CSR file for generating your certificates. Finally, the Config folder would include any JSON configuration files used by the Azure Stack Hub installer.
Infrastructure Folder Structure
Once Azure Stack Hub is deployed, it’s critical to maintain a folder structure for your infrastructure blueprint files, which may include Resource Manager templates, PowerShell scripts, and DSC configurations. Here’s an example of how such a structure might look:
AzureStackInfrastructure
│
├───Templates
│ ├───VMs
│ ├───Storage
│ ├───Networking
│ └───PaaSResources
├───Scripts
│ ├───DeploymentScripts
│ └───MaintenanceScripts
└───DSC
└───NodeConfigurations
In this structure, Templates contains ARM templates organized according to the type of resource they represent. Scripts has PowerShell scripts used for deploying and maintaining resources. DSC refers to Desired State Configuration scripts that ensure that the environment maintains a specific state.
Backup Folder Structure
Azure Stack Hub backup procedures typically demand a structure to hold the backup data. It is often segregated by the scope and the type of backup such as:
AzureStackBackups
│
├───InfrastructureBackups
│ ├───Fabric
│ ├───Storage
│ └───IaaSVMs
└───UserResourceBackups
├───TenantWorkloads
└───AppServices
InfrastructureBackups would contain all backups related to the core Azure Stack Hub system, such as hardware lifecycle host, storage spaces direct, and infrastructure VMs. UserResourceBackups holds the backups related to tenant workloads and PaaS resources.
Logs and Diagnostic Data Folder Structure
When troubleshooting or monitoring the Azure Stack Hub environment, you will need a folder for logs and diagnostic data:
AzureStackDiagnostics
│
├───Logs
│ ├───DeploymentLogs
│ ├───ResourceProviderLogs
│ └───AuditLogs
└───Metrics
└───PerformanceData
In the Logs directory, you’ll collect logs from various sources, such as deployment or operations. Metrics can store performance data gathered from the system for analysis.
Marketplace Management Folder Structure
If managing the Azure Stack Hub Marketplace is part of your role, then maintaining an organized folder for marketplace items is essential:
AzureStackMarketplace
│
├───Items
│ ├───ResourceTemplates
│ ├───Extensions
│ └───VMImages
└───SyndicationTools
└───SyndicationScripts
The Items folder would be for storing ARM templates, VM extensions, and VM images available in your marketplace. In SyndicationTools, you would store the scripts used for syndicating items from Azure to Azure Stack Hub.
By maintaining these structured folders, Azure Stack Hub administrators can ensure that all components are organized, which facilitates efficient operations, management, and troubleshooting of the hybrid cloud environment. A well-prepared folder structure is critical not only for successfully passing the AZ-600 exam but also for effective real-world management of Azure Stack Hub.
Practice Test with Explanation
True or False: In Azure Stack Hub, resource groups are used to organize related resources for an application into a single folder structure.
- True
- False
Answer: True
Explanation: Resource groups in Azure Stack Hub are indeed used to organize related resources for an application into a group that can be managed and monitored together, acting as a folder structure for organization.
True or False: When preparing a folder structure in Azure Stack Hub, you can create nested resource groups within a resource group.
- True
- False
Answer: False
Explanation: Azure Stack Hub, like Azure, does not support the nesting of resource groups within each other. A resource group is a flat structure where all resources are peers.
Which file format is typically used for defining Azure Resource Manager (ARM) templates?
- JSON
- XML
- CSV
- TXT
Answer: JSON
Explanation: ARM templates are written in JavaScript Object Notation (JSON) file format.
True or False: ARM templates can be stored in any storage account, regardless of whether it is part of Azure Stack Hub or an external storage service.
- True
- False
Answer: True
Explanation: ARM templates are just JSON files and can be stored in any accessible storage solution as long as they can be retrieved by the Azure Stack Hub for deployment.
When organizing storage in Azure Stack Hub, which service would you specifically use to create file shares that can be accessed using the Server Message Block (SMB) protocol?
- Azure Blob Storage
- Azure Table Storage
- Azure Queue Storage
- Azure Files
Answer: Azure Files
Explanation: Azure Files offers fully managed file shares in the cloud that are accessible via the SMB protocol.
True or False: You should always store ARM templates in the same resource group where the resources will be deployed.
- True
- False
Answer: False
Explanation: ARM templates can be stored in any location, such as a source control repository, a storage account, or a local directory, and not necessarily in the resource group where resources will be deployed.
Which of the following is a best practice when preparing a folder structure for deploying resources in Azure Stack Hub?
- Mix development and production assets in the same resource groups for ease of access.
- Hard-code all values in ARM templates for consistency across deployments.
- Categorize and organize resources by lifecycle and purpose using naming conventions.
- Use a flat structure with no tagging for simplicity.
Answer: Categorize and organize resources by lifecycle and purpose using naming conventions.
Explanation: Best practices involve categorizing and organizing resources by lifecycle and purpose, using clear naming conventions and other organizational tools like tags to maintain order and ease management.
True or False: It is advised to separate resources for production and non-production environments when preparing folder structures in Azure Stack Hub.
- True
- False
Answer: True
Explanation: Separating resources for production and non-production environments provides clarity and reduces risks of unintended changes or deletions in the production environment.
In Azure Stack Hub, which concept allows you to group and manage related resources together?
- Subscriptions
- Management groups
- Resource groups
- Virtual networks
Answer: Resource groups
Explanation: Resource groups in Azure Stack Hub are used to group and manage related resources for an application or a solution together.
When preparing a folder structure in Azure Stack Hub, which of the following is an advisable naming convention for naming resources?
- Use as few characters as possible to save space.
- Include the environment, region, and application in the name.
- Use the administrator’s name for easy identification.
- Keep naming random for security purposes.
Answer: Include the environment, region, and application in the name.
Explanation: A logical naming convention, which may include the environment, region, and application, helps in the organization and management of resources.
True or False: Azure Stack Hub supports the deployment of resources using both ARM templates and scripts like PowerShell or Azure CLI.
- True
- False
Answer: True
Explanation: Azure Stack Hub supports deploying resources using ARM templates, as well as automation scripts like PowerShell and Azure CLI.
To ensure consistency, how should deployment artifacts such as ARM templates and parameter files be managed in Azure Stack Hub?
- Managed manually by the administrator on their local machine.
- Stored on local file shares for exclusive admin access.
- Stored and version-controlled in a source control system such as Azure DevOps or GitHub.
- Each deployment should create new, custom templates.
Answer: Stored and version-controlled in a source control system such as Azure DevOps or GitHub.
Explanation: Storing deployment artifacts in a version-controlled source control system helps to maintain consistency, track changes, and collaborate effectively among team members.
Creating a good folder structure for AZ-600 can save a lot of time during revision. Does anyone have a sample structure?
I also include a Resources folder in each module for quick access to links and documents.
Thanks for this blog post!
Anybody here using OneDrive to sync their folder structure?
I keep a separate folder for past papers and exam dumps. Helps a lot during the final revision.
Anyone here using tags within folders?
What tool are you all using to create your folder structure?
I suggest having a folder just for PowerShell scripts related to Azure Stack Hub.