Detailed Solution:
In an Entra ID abuse path, a privileged user such as User Administrator may reset another user's password. In logs, this appears as a user update operation involving the password profile.
Check audit logs in the portal:
Microsoft Entra ID # Monitoring # Audit logs
Or query via Microsoft Graph/Azure tooling depending on permissions.
The activity to look for is generally:
Update user
Modified property: passwordProfile
The other options represent different activities:
Microsoft.Authorization/roleAssignments/write = RBAC role assignment change Microsoft.Storage/storageAccounts/listKeys/action = storage account key retrieval Microsoft.KeyVault/vaults/secrets/read = Key Vault secret read Correct answer:
B). Update user / password profile modification

Detailed Solution:
From Q7, you should recover a limited-access SAS token or storage access information.
Set the storage account name and SAS token:
ACCOUNT= " excaliburstore "
SAS= " < recovered-sas-token > "
List containers:
az storage container list \
--account-name " $ACCOUNT " \
--sas-token " $SAS " \
--output table
The available container is:
sensitive-files
You can also confirm directly:
az storage blob list \
--account-name " $ACCOUNT " \
--container-name sensitive-files \
--sas-token " $SAS " \
--output table
Final answer:
C). sensitive-files

Detailed Solution:
List NSG rules:
az network nsg rule list \
--resource-group rg-prod-apps-eastus \
--nsg-name nsg-prod-linux01 \
--output table
Expected risky rule:
Name Priority Direction Access Protocol Source DestinationPortRange
------------ -------- --------- ------ -------- ------------ -------------------- Allow-SSH 100 Inbound Allow Tcp Internet 22 SSH exposed directly to the Internet is risky because it increases brute-force, credential-stuffing, and remote exploitation exposure. In a hardened Azure environment, SSH should typically be restricted through VPN, Bastion, JIT access, or trusted administrative IP ranges.
Correct answer:
B). Allow TCP 22 from Internet

Detailed Solution:
Log in using the credential recovered in Q4.
az login -u [email protected] -p ' < recovered-password > ' Confirm the current signed-in user:
az ad signed-in-user show --output json
Now enumerate the user's Microsoft Entra ID role memberships through Microsoft Graph.
az rest --method GET \
--url " https://graph.microsoft.com/v1.0/me/memberOf " \
--output json
To display only role names:
az rest --method GET \
--url " https://graph.microsoft.com/v1.0/me/memberOf " \
--query " value[].displayName " \
--output table
The relevant role is:
User Administrator
This role is dangerous because it can manage users and reset passwords for many non-privileged users. That is exactly why the next task asks you to abuse directory-level privileges to compromise another user.
Final answer:
B). User Administrator

Detailed Solution:
Resolve the service principal object ID:
az ad sp show \
--id c5fba7db-5e61-45bc-8944-3cd457bb19c2 \
--query id \
--output tsv
Then list role assignments:
SP_OBJECT_ID=$(az ad sp show \
--id c5fba7db-5e61-45bc-8944-3cd457bb19c2 \
--query id \
--output tsv)
az role assignment list \
--assignee " $SP_OBJECT_ID " \
--all \
--output table
Expected output:
Principal Role Scope
------------------------------------ ----------- ----------------------------------------
< sp-object-id > Contributor /subscriptions/5d8e44ac-...
Correct answer:
B). Contributor