Question 90
A security scan flags resource-group-wide AI role assignments that were only needed for one resource. What should change?
- Keep a verified alternate credential and audit cutover before revoking the exposed key
- Acquire short-lived tokens at runtime through the managed-identity credential chain
- Grant the caller permission to read the secret using the vault's chosen authorization model
- Scope the role assignment to that individual resource where feasible
Explanation
Correct Answer
D:RBAC inheritance makes broad assignments effective on multiple resources; narrower scope reduces unnecessary exposure. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after scoping the role assignment to that individual resource where feasible.
Incorrect Answers
A:Rollback should restore authorized connectivity through a known safe credential, not re-enable a compromised secret in its own workflow, but that is a different correction from the present requirement to scope the role assignment to that individual resource where feasible. The reported issue would remain.
B:That change addresses another failure mode: access tokens expire and are not durable application secrets; supported credentials renew them when needed; it does not address this case, for which the relevant intervention is to scope the role assignment to that individual resource where feasible.
C:Although useful elsewhere in the regulated Azure AI application, knowing a secret's URI does not grant access; RBAC or vault access policy controls the read operation; the present case is different and calls for the team to scope the role assignment to that individual resource where feasible.
Question 91
A team responsible for a regulated Azure AI application needs to replace compromised shared service keys without prolonged application interruption; the acceptance check is that the application keeps operating after the old credential is revoked. Which capability should be selected?
- Store API keys in Azure Key Vault
- Use Microsoft Entra managed-identity authentication
- Configure a private endpoint
- Assign appropriate Azure RBAC roles
- Apply key rotation and credential rollback procedures
Explanation
Correct Answer
E:Coordinated key rotation updates consumers and changes active credentials, commonly using alternate keys where supported. For this regulated Azure AI application, the intended evidence is that the application keeps operating after the old credential is revoked. It does not fix a missing model deployment or an unauthorized Entra principal.
Incorrect Answers
A:Key Vault centralizes secret storage and access policies or RBAC for clients allowed to retrieve credentials; it may be used to protect and rotate service credentials away from application source code in a regulated Azure AI application, but the current requirement is instead to replace compromised shared service keys without prolonged application interruption. That separate capability does not prove that the application keeps operating after the old credential is revoked; Secret storage does not convert an API-key authorization flow into Entra authorization, so selecting that alternative would not meet the stated acceptance check.
B:A managed identity obtains Entra tokens for a workload and requires appropriate resource RBAC permissions to authorize access; it may be used to allow Azure-hosted code to call a compatible AI resource without storing a shared API key in a regulated Azure AI application, but the current requirement is instead to replace compromised shared service keys without prolonged application interruption. That separate capability does not prove that the application keeps operating after the old credential is revoked; Identity by itself does not remove public network exposure or grant every data action, so selecting that alternative would not meet the stated acceptance check.
C:Private endpoints map supported service access to a private IP in a VNet, alongside required DNS and network controls; it may be used to provide private-network connectivity to an AI resource from an approved virtual network in a regulated Azure AI application, but the current requirement is instead to replace compromised shared service keys without prolonged application interruption. That separate capability does not prove that the application keeps operating after the old credential is revoked; Private Link does not replace authentication or decide a user's RBAC privileges, so selecting that alternative would not meet the stated acceptance check.
D:Azure RBAC assignments combine a principal, role definition, and scope to authorize supported management or data operations; it may be used to grant a principal the minimum resource permissions required for its AI operations in a regulated Azure AI application, but the current requirement is instead to replace compromised shared service keys without prolonged application interruption. That separate capability does not prove that the application keeps operating after the old credential is revoked; Assigning a role does not establish an encrypted private network path by itself, so selecting that alternative would not meet the stated acceptance check.
Question 92
Key rotation was completed but the app still returns 401 after a restart. What component is most likely stale?
- Use a role that grants the required AI service data actions, not only management read access
- Inspect the deployed application's cached key or secret reference and refresh it
- Check that the identity has the required data-plane role on the AI resource
- Restrict public network access according to the resource's supported networking controls
Explanation
Correct Answer
B:Rotating the resource credential is insufficient when the client still sends the prior revoked value. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after inspecting the deployed application's cached key or secret reference and refresh it.
Incorrect Answers
A:That change addresses another failure mode: management-plane visibility and data-plane inference permissions are separate authorization concerns; it does not address this case, for which the relevant intervention is to inspect the deployed application's cached key or secret reference and refresh it.
C:Although useful elsewhere in the regulated Azure AI application, obtaining a token proves authentication; authorization can still fail when the principal lacks a suitable role or scope; the present case is different and calls for the team to inspect the deployed application's cached key or secret reference and refresh it.
D:Creating a private endpoint does not necessarily disable the public access path; both must be governed deliberately in its own workflow, but that is a different correction from the present requirement to inspect the deployed application's cached key or secret reference and refresh it. The reported issue would remain.
Question 93
Developers need to invoke an inference endpoint but must not change resource configuration. What grant design is appropriate?
- Assign the least-privileged supported data-plane inference role at the narrowest useful scope
- Enable the Function's managed identity and request a resource-scoped Entra token
- Switch clients to the unused key, validate traffic, then regenerate the old key
- Configure private endpoint connectivity and the corresponding private DNS resolution
Explanation
Correct Answer
A:Administrative Contributor permissions are broader than inference access; role scope and allowed actions should match the runtime task. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after assigning the least-privileged supported data-plane inference role at the narrowest useful scope.
Incorrect Answers
B:Although useful elsewhere in the regulated Azure AI application, managed identity avoids a long-lived shared key, but the identity still needs the correct resource permissions; the present case is different and calls for the team to assign the least-privileged supported data-plane inference role at the narrowest useful scope.
C:That change addresses another failure mode: dual-key rotation limits downtime because applications can continue using a valid key while the compromised key is revoked; it does not address this case, for which the relevant intervention is to assign the least-privileged supported data-plane inference role at the narrowest useful scope.
D:Private Link requires correct endpoint routing and DNS; a private endpoint object alone does not force clients to resolve private IPs in its own workflow, but that is a different correction from the present requirement to assign the least-privileged supported data-plane inference role at the narrowest useful scope. The reported issue would remain.
Question 94
An application repeatedly fails to read a vault secret despite knowing the vault URL. What must be checked?
- Grant the caller permission to read the secret using the vault's chosen authorization model
- Scope the role assignment to that individual resource where feasible
- Check peering, routes, private DNS reachability, and applicable network policies
- Keep a verified alternate credential and audit cutover before revoking the exposed key
Explanation
Correct Answer
A:Knowing a secret's URI does not grant access; RBAC or vault access policy controls the read operation. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after granting the caller permission to read the secret using the vault's chosen authorization model.
Incorrect Answers
B:Although useful elsewhere in the regulated Azure AI application, rBAC inheritance makes broad assignments effective on multiple resources; narrower scope reduces unnecessary exposure; the present case is different and calls for the team to grant the caller permission to read the secret using the vault's chosen authorization model.
C:That change addresses another failure mode: successful private connectivity depends on actual network paths and name resolution from each client network; it does not address this case, for which the relevant intervention is to grant the caller permission to read the secret using the vault's chosen authorization model.
D:Rollback should restore authorized connectivity through a known safe credential, not re-enable a compromised secret in its own workflow, but that is a different correction from the present requirement to grant the caller permission to read the secret using the vault's chosen authorization model. The reported issue would remain.
Question 95
The solution brief for a regulated Azure AI application requires the system to provide private-network connectivity to an AI resource from an approved virtual network. A successful test confirms that resolution and traffic use the intended private network path. What should the team use?
- Apply key rotation and credential rollback procedures
- Store API keys in Azure Key Vault
- Use Microsoft Entra managed-identity authentication
- Configure a private endpoint
Explanation
Correct Answer
D:Private endpoints map supported service access to a private IP in a VNet, alongside required DNS and network controls. For this regulated Azure AI application, the intended evidence is that resolution and traffic use the intended private network path. Private Link does not replace authentication or decide a user's RBAC privileges.
Incorrect Answers
A:Coordinated key rotation updates consumers and changes active credentials, commonly using alternate keys where supported; it may be used to replace compromised shared service keys without prolonged application interruption in a regulated Azure AI application, but the current requirement is instead to provide private-network connectivity to an AI resource from an approved virtual network. That separate capability does not prove that resolution and traffic use the intended private network path; It does not fix a missing model deployment or an unauthorized Entra principal, so selecting that alternative would not meet the stated acceptance check.
B:Key Vault centralizes secret storage and access policies or RBAC for clients allowed to retrieve credentials; it may be used to protect and rotate service credentials away from application source code in a regulated Azure AI application, but the current requirement is instead to provide private-network connectivity to an AI resource from an approved virtual network. That separate capability does not prove that resolution and traffic use the intended private network path; Secret storage does not convert an API-key authorization flow into Entra authorization, so selecting that alternative would not meet the stated acceptance check.
C:A managed identity obtains Entra tokens for a workload and requires appropriate resource RBAC permissions to authorize access; it may be used to allow Azure-hosted code to call a compatible AI resource without storing a shared API key in a regulated Azure AI application, but the current requirement is instead to provide private-network connectivity to an AI resource from an approved virtual network. That separate capability does not prove that resolution and traffic use the intended private network path; Identity by itself does not remove public network exposure or grant every data action, so selecting that alternative would not meet the stated acceptance check.
Question 96
A pipeline logs a complete Key Vault secret after reading it for a connectivity test. Which security fix is essential?
- Inspect the deployed application's cached key or secret reference and refresh it
- Restrict public network access according to the resource's supported networking controls
- Use a role that grants the required AI service data actions, not only management read access
- Redact secret values from application and deployment logs
Explanation
Correct Answer
D:Secure storage is undermined if retrieved credentials are written into accessible telemetry. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after redacting secret values from application and deployment logs.
Incorrect Answers
A:That change addresses another failure mode: rotating the resource credential is insufficient when the client still sends the prior revoked value; it does not address this case, for which the relevant intervention is to redact secret values from application and deployment logs.
B:Although useful elsewhere in the regulated Azure AI application, creating a private endpoint does not necessarily disable the public access path; both must be governed deliberately; the present case is different and calls for the team to redact secret values from application and deployment logs.
C:Management-plane visibility and data-plane inference permissions are separate authorization concerns in its own workflow, but that is a different correction from the present requirement to redact secret values from application and deployment logs. The reported issue would remain.
Question 97
A compromised service key must be replaced, but the resource exposes two interchangeable keys. What is the safest rotation order?
- Store the service key in Key Vault and retrieve it using a controlled application identity
- Configure private endpoint connectivity and the corresponding private DNS resolution
- Assign the least-privileged supported data-plane inference role at the narrowest useful scope
- Switch clients to the unused key, validate traffic, then regenerate the old key
Explanation
Correct Answer
D:Dual-key rotation limits downtime because applications can continue using a valid key while the compromised key is revoked. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after switching clients to the unused key, validate traffic, then regenerate the old key.
Incorrect Answers
A:Key Vault separates secret storage from source code and supports access policies and auditing in its own workflow, but that is a different correction from the present requirement to switch clients to the unused key, validate traffic, then regenerate the old key. The reported issue would remain.
B:Although useful elsewhere in the regulated Azure AI application, private Link requires correct endpoint routing and DNS; a private endpoint object alone does not force clients to resolve private IPs; the present case is different and calls for the team to switch clients to the unused key, validate traffic, then regenerate the old key.
C:That change addresses another failure mode: administrative Contributor permissions are broader than inference access; role scope and allowed actions should match the runtime task; it does not address this case, for which the relevant intervention is to switch clients to the unused key, validate traffic, then regenerate the old key.
Question 98
The app must temporarily keep using a key-based legacy API, and auditors prohibit storing keys in a repository. Where should the key reside?
- Store the service key in Key Vault and retrieve it using a controlled application identity
- Switch clients to the unused key, validate traffic, then regenerate the old key
- Enable the Function's managed identity and request a resource-scoped Entra token
- Assign the least-privileged supported data-plane inference role at the narrowest useful scope
Explanation
Correct Answer
A:Key Vault separates secret storage from source code and supports access policies and auditing. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after storing the service key in Key Vault and retrieve it using a controlled application identity.
Incorrect Answers
B:That change addresses another failure mode: dual-key rotation limits downtime because applications can continue using a valid key while the compromised key is revoked; it does not address this case, for which the relevant intervention is to store the service key in Key Vault and retrieve it using a controlled application identity.
C:Managed identity avoids a long-lived shared key, but the identity still needs the correct resource permissions in its own workflow, but that is a different correction from the present requirement to store the service key in Key Vault and retrieve it using a controlled application identity. The reported issue would remain.
D:Although useful elsewhere in the regulated Azure AI application, administrative Contributor permissions are broader than inference access; role scope and allowed actions should match the runtime task; the present case is different and calls for the team to store the service key in Key Vault and retrieve it using a controlled application identity.
Question 99
A security team wants to ensure emergency credential rollback does not silently reactivate a compromised key. What should the runbook emphasize?
- Scope the role assignment to that individual resource where feasible
- Keep a verified alternate credential and audit cutover before revoking the exposed key
- Grant the caller permission to read the secret using the vault's chosen authorization model
- Check peering, routes, private DNS reachability, and applicable network policies
Explanation
Correct Answer
B:Rollback should restore authorized connectivity through a known safe credential, not re-enable a compromised secret. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after keeping a verified alternate credential and audit cutover before revoking the exposed key.
Incorrect Answers
A:That change addresses another failure mode: rBAC inheritance makes broad assignments effective on multiple resources; narrower scope reduces unnecessary exposure; it does not address this case, for which the relevant intervention is to keep a verified alternate credential and audit cutover before revoking the exposed key.
C:Knowing a secret's URI does not grant access; RBAC or vault access policy controls the read operation in its own workflow, but that is a different correction from the present requirement to keep a verified alternate credential and audit cutover before revoking the exposed key. The reported issue would remain.
D:Although useful elsewhere in the regulated Azure AI application, successful private connectivity depends on actual network paths and name resolution from each client network; the present case is different and calls for the team to keep a verified alternate credential and audit cutover before revoking the exposed key.
Question 100
A managed-identity request receives 403 even though an access token was issued. Where should the engineer look?
- Restrict public network access according to the resource's supported networking controls
- Use a role that grants the required AI service data actions, not only management read access
- Redact secret values from application and deployment logs
- Check that the identity has the required data-plane role on the AI resource
Explanation
Correct Answer
D:Obtaining a token proves authentication; authorization can still fail when the principal lacks a suitable role or scope. In the regulated Azure AI application, confirm the fix by retesting the affected behavior after checking that the identity has the required data-plane role on the AI resource.
Incorrect Answers
A:Although useful elsewhere in the regulated Azure AI application, creating a private endpoint does not necessarily disable the public access path; both must be governed deliberately; the present case is different and calls for the team to check that the identity has the required data-plane role on the AI resource.
B:Management-plane visibility and data-plane inference permissions are separate authorization concerns in its own workflow, but that is a different correction from the present requirement to check that the identity has the required data-plane role on the AI resource. The reported issue would remain.
C:That change addresses another failure mode: secure storage is undermined if retrieved credentials are written into accessible telemetry; it does not address this case, for which the relevant intervention is to check that the identity has the required data-plane role on the AI resource.