Explanation:
No, No, Yes
In Microsoft Azure Active Directory (Azure AD), the Self-Service Password Reset (SSPR) feature allows users to securely reset their passwords using preconfigured authentication methods. The configuration in this scenario specifies:
* Number of methods required to reset: 2
* Available methods: Mobile phone and Security questions
* Number of questions required to register: 3
* Number of questions required to reset: 3
However, the key detail lies in the user types and roles involved:
* SecAdmin1 (Security Administrator) and BillAdmin1 (Billing Administrator) are Azure AD administrators.
* Azure AD documentation explicitly states that administrative accounts (users with Azure AD admin roles such as Global Administrator, Security Administrator, Billing Administrator, or other privileged roles) cannot use security questions as an authentication method for SSPR.
* Admins are required to use stronger methods, such as phone, email, or app-based authentication (MFA-enabled).
* Therefore, both SecAdmin1 and BillAdmin1 will not use security questions for password reset.
* User1 (Reports reader) is a standard user, not an administrator.
* Standard users can use security questions as one of their authentication methods.
* Since security questions are enabled and three questions are required to reset the password, User1 must answer all three - including "What was the name of your first pet?" Thus, according to Azure AD SSPR policy as covered in the Microsoft Learn AZ-104 study guide and official documentation under "Self-service password reset for administrators" and "Authentication methods in Azure Active Directory", only non-administrative users can use security questions for SSPR.

Explanation:

Explanation:
Data Sources: VM1 only
Destination: Workspace1 Only

When deploying an Azure Container Instance (ACI) using an image from an Azure Container Registry (ACR), the deployment must authenticate to the registry to pull the image. By default, ACR is secured, and you cannot pull images anonymously unless they are public.
According to the Azure Administrator study guide, enabling the Admin user option in ACR generates two access credentials (username and password) that can be used for authentication when pulling container images. When the Admin user setting is disabled, you cannot authenticate directly using those credentials, and automated deployments may fail with authentication errors.
By enabling the Admin user setting, Azure creates a service-level user account for the registry with permissions to push and pull images. These credentials can then be referenced securely in your container instance configuration - either through the Azure portal, ARM template, or CLI parameters such as -- registry-username and --registry-password.
This configuration allows ACI to authenticate successfully against the ACR and pull the required image (image1) for deployment.
Therefore, enabling the Admin user for the container registry meets the goal of allowing the deployment of the container instance using image1.

Explanation:

Box 1: Create a virtual network gateway and a local network gateway.
Azure VPN gateway. The VPN gateway service enables you to connect the VNet to the on-premises network through a VPN appliance. For more information, see Connect an on-premises network to a Microsoft Azure virtual network. The VPN gateway includes the following elements:
Virtual network gateway. A resource that provides a virtual VPN appliance for the VNet. It is responsible for routing traffic from the on-premises network to the VNet.
Local network gateway. An abstraction of the on-premises VPN appliance. Network traffic from the cloud application to the on-premises network is routed through this gateway.
Connection. The connection has properties that specify the connection type (IPSec) and the key shared with the on-premises VPN appliance to encrypt traffic.
Gateway subnet. The virtual network gateway is held in its own subnet, which is subject to various requirements, described in the Recommendations section below.
Box 2: Configure a site-to-site VPN connection
On premises create a site-to-site connection for the virtual network gateway and the local network gateway.

Scenario: Connect the New York office to VNet1 over the Internet by using an encrypted connection.