Practice Test #1

Azure Advisor cannot be relied on to generate a definitive list of Azure virtual machines that are protected by Azure Backup. Advisor’s purpose is to provide recommendations (for example, “enable backup for VMs” if it detects VMs without backup), not to serve as an authoritative reporting inventory of backup-protected resources. To list which VMs are protected, you would typically use Recovery Services vault/Backup center views, Azure Backup reports, or queries via Azure Resource Graph/Log Analytics depending on your reporting needs. Those tools are designed to show protection status, backup items, and compliance across subscriptions. Therefore, the statement is false: Advisor may highlight missing backups as a recommendation, but it does not function as the primary mechanism to generate a complete list of VMs currently protected by Azure Backup.

Implementing security recommendations increases your company’s Secure Score; it does not decrease it. Secure Score is a Microsoft Defender for Cloud metric that reflects your security posture based on implemented controls and remediated recommendations. As you address recommendations (e.g., enabling MFA, applying just-in-time VM access, enabling Defender plans, fixing NSG rules), your score typically goes up because you reduce risk and close security gaps. Azure Advisor can surface security recommendations, but the scoring concept is tied to Defender for Cloud. The directionality is important for the exam: remediation improves posture and raises Secure Score. So the statement is false because it claims the score will decrease when implementing recommendations, which is the opposite of how Secure Score works.

There is no Microsoft policy requiring you to implement Azure Advisor security recommendations within 30 days to maintain Microsoft support. Azure Advisor recommendations are best-practice guidance intended to help optimize and secure workloads; they are optional and prioritized based on impact. Microsoft support eligibility is not contingent on implementing Advisor recommendations by a fixed deadline. Support requirements are generally related to using supported products/versions, maintaining proper licensing, and meeting contractual terms—not remediating advisory guidance within a specific timeframe. In regulated environments, an organization may set internal SLAs (e.g., remediate high-severity findings within 30 days) using governance tools like Azure Policy, Defender for Cloud regulatory compliance, or ITSM processes, but that is a customer-defined control, not a Microsoft support mandate. Therefore, the statement is false.

Correct is B (portal.) because the Azure portal is accessed at https://portal.azure.com and is the standard web interface to manage all Azure resources across subscriptions, resource groups, and services (including all 10 web apps). The portal is part of the Azure management plane and integrates governance capabilities such as RBAC, policy, resource locks, and cost management. A (admin.) is not the standard subdomain for Azure’s global management portal. While some services may have admin-related endpoints in other Microsoft products, Azure resource management is not done via an admin.azure.com URL. C (www.) is a common public website prefix but is not used for the Azure portal. Using www.azure.com would take you to marketing/documentation pages, not the authenticated management experience required to administer resources.

Correct is A (azure.) because the full portal URL is portal.azure.com. The domain azure.com is used for Azure’s primary web presence and includes the authenticated portal endpoint. B (azurewebsites.) is associated with Azure App Service default application hostnames (for example, <appname>.azurewebsites.net). That domain is for accessing the deployed web application (data plane / app endpoint), not for managing all Azure resources. You might use it to browse a specific web app, but not to administer subscriptions, resource groups, networking, identities, etc. C (microsoft.) is not the domain used for the Azure portal. Although Microsoft owns Azure, the portal is not hosted at portal.microsoft.com for Azure resource management in this context.

No. A service in private preview is not released to all Azure customers. Private preview is intentionally limited to a small, selected group—often by invitation, application, or nomination—so Microsoft can validate functionality, performance, security, and usability with controlled feedback. In private preview, features may be incomplete, documentation may be limited, and breaking changes are more likely. It typically does not include an SLA and is not intended for broad production use. Because access is restricted, it cannot be considered “released to all Azure customers.” Why “Yes” is wrong: “released to all customers” aligns more closely with public preview (opt-in) or general availability (fully released), not private preview. Private preview is the most restricted stage in the release lifecycle.

Yes. A service in public preview is generally available for Azure customers to try, meaning it is released broadly rather than to a hand-picked subset. In public preview, customers can typically enable or deploy the service themselves (opt-in), though there may be limitations such as supported regions, specific subscription types, quotas, or feature gaps. Public preview is still pre-release from a production standpoint: Microsoft often provides it without an SLA and may recommend against mission-critical production workloads. However, the key exam concept is that public preview is open to the public (Azure customers) rather than invitation-only. Why “No” is wrong: “No” would describe private preview (restricted access). Public preview expands access beyond a limited pilot group, even if it’s not available in every region or for every scenario yet.

No. General availability (GA) means the service is fully released for production use and is broadly available to Azure customers. GA typically comes with full supportability and, where applicable, a published SLA. The defining characteristic is that it is no longer a preview and is considered ready for mainstream adoption. While Microsoft may sometimes roll out GA features progressively by region or cloud (public vs sovereign), GA is not described as being released only to a subset of customers. A “subset of customers” aligns more with private preview (invite-only) or limited preview programs. Why “Yes” is wrong: If a service is only available to a subset of customers, it is not truly GA; it would more accurately be categorized as private preview or a limited/controlled release rather than general availability.