Azure AZ-600 flashcards
Azure AZ-600 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Azure Stack Hub deployment identity choice
- At deployment the operator selects Azure AD or AD FS as the identity provider. Azure AD enables multi-tenant and Azure-consistent sign-in; AD FS supports disconnected environments with local accounts.
- Scale unit node count
- The number of physical servers in a scale unit determines resiliency and capacity. The OEM validates the supported minimum and maximum node counts for the specific hardware model.
- External domain name immutability
- The external domain name chosen during deployment is fixed. Changing it requires redeployment, so DNS names and certificates must be finalized before cloud builder runs.
- Public VIP pool
- A range of public IP addresses reserved at deployment for tenant public IPs and infrastructure service endpoints. Its size limits how many public IPs tenants can allocate.
- Connected vs disconnected mode
- Connected stamps register with Azure for billing and marketplace syndication. Disconnected stamps use capacity-model billing and require offline marketplace publishing.
- Certificate pre-deployment check
- Before deployment, certificates for portal, admin portal, ARM, and service endpoints are validated against the external domain name using the deployment checker to catch name mismatches early.
- OEM firmware responsibility
- Firmware and driver updates for the physical hosts are delivered and applied per the hardware vendor's process, separate from Azure Stack Hub software updates.
- Region vs scale unit
- A region is the deployment boundary containing one or more scale units. Each scale unit adds compute and storage capacity to the same region and stamp.
- Plan and offer relationship
- A plan groups services with quotas; an offer publishes one or more plans to tenants. Tenants subscribe to offers, and subscriptions inherit the plan quotas.
- Quota enforcement behavior
- Quotas cap consumption per service per subscription. When a quota is reached, new resource creation in that service fails until the quota is raised or resources are deleted.
- Private offer access
- A private offer is not visible to all tenants. The operator must explicitly add each tenant subscription before that tenant can subscribe to the offer.
- Delegated provider model
- A delegated provider receives a delegated offer from the operator and can create its own plans and offers, managing tenants within its own organization.
- Marketplace syndication
- Connected stamps download marketplace items from Azure. Disconnected stamps use the marketplace syndication tool to download and publish items to the local marketplace.
- Resource provider registration
- Each tenant subscription must register the resource providers for the resource types it uses, such as Compute, Storage, Network, and Web, before creating those resources.
- Supported PaaS on Azure Stack Hub
- PaaS availability depends on installed resource providers. App Service, SQL and MySQL, Event Hubs, Service Fabric, and Kubernetes are optional and must be deployed by the operator.
- Base services in a plan
- Compute, storage, and network are the base services included in a plan. Additional services are added to the plan as the operator enables them.
- Tenant RBAC scope levels
- Azure Stack Hub supports built-in roles such as Owner, Contributor, and Reader assigned at subscription, resource group, or resource scope, mirroring Azure role-based access control.
- Offer publication state
- An offer must be published before tenants can see and subscribe to it. Changing plans in an offer may require republishing for the change to take effect.
- Add-on plans
- Add-on plans are attached to an existing subscription rather than offered standalone. They let the operator grant extra quota or services to selected tenants.
- Privileged endpoint connection
- Operators connect with Enter-PSSession using the ERCS IP and the PrivilegedEndpoint configuration name, authenticating with a cloud admin account to run stamp management commands.
- ERCS VM count
- The ERCS role hosts the privileged endpoint. The number of ERCS VMs equals the scale unit node count plus one, and they reside on the infrastructure subnet.
- Test-AzureStack cmdlet
- Run from the privileged endpoint, Test-AzureStack validates infrastructure health. The -Group parameter limits checks and -IncludePassed shows successful checks too.
- Infrastructure backup scope
- Infrastructure backup captures control-plane configuration to an SMB share. It does not include tenant VMs or tenant data, which tenants must protect separately.
- Backup before update rule
- A successful infrastructure backup must exist before applying an update. The backup enables recovery of the stamp's control plane if the update fails.
- Get-AzureStackLog usage
- This privileged endpoint cmdlet collects logs from stamp roles for support cases. The -FilterByRole parameter targets roles such as BareMetal, Infrastructure, or Storage.
- Alert remediation guidance
- Administrator portal alerts include description and remediation steps. Operators can view active and historical alerts and close them after resolving the underlying condition.
- Update package application
- Updates are downloaded, validated with Test-AzureStack, then applied from the administrator portal. Progress and state are visible in the update blade until completion.
- Cloud admin account role
- The cloud admin account is created at deployment and has operator rights on the stamp. It is used for the administrator portal and privileged endpoint sessions.
- Region capacity blade
- The administrator portal capacity view shows physical and allocated capacity per service, helping operators decide when to add a scale unit or adjust quotas.
- Usage data and billing
- Connected stamps send usage data to Azure for billing against the subscription. Disconnected stamps export usage data that the operator reports under the capacity model.
- Hotfix vs full update
- Full package updates deliver the next major build. Hotfixes address specific issues within a build and are applied through the same update mechanism.
- Stamp information query
- Get-AzureStackStampInformation from the privileged endpoint returns build version, region, and stamp details, useful for verifying the deployed release before an update.