Microsoft AI-103 Practice Test 19 - Prepaway
Practice Exams:

Pass Microsoft AI-103 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$89.99 $98.99

AI-103 Premium ETE File


  • Premium File 187 Questions & Answers. Last Update: Nov 15, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-103 Practice Test 19

Question 180

Situation: An airline concierge sees p95 latency increase during a model refresh and needs a quick rollback without editing every client. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path
  2. Swap every production endpoint to an untested model snapshot simultaneously
  3. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached
  4. Inspect records that explain the affected process, then check the result described in this case: An airline concierge sees p95 latency increase during a model refresh and needs a quick rollback without editing every client
  5. Remove the previous model version before observing the canary

Explanation

Correct Answer

B:

An airline concierge sees p95 latency increase during a model refresh and needs a quick rollback without editing every client. “Swap every production endpoint to an untested model snapshot simultaneously” would violate the requirement. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

E:

Because an airline concierge sees p95 latency increase during a model refresh and needs a quick rollback without editing every client, “Remove the previous model version before observing the canary” would violate the requirement. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Incorrect Answers

A:

“Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path” is the controlled implementation, not an unsafe workaround. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Confirm that canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

C:

An airline concierge sees p95 latency increase during a model refresh and needs a quick rollback without editing every client. “Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached” is the required outcome of a working control, not an action that weakens it. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

D:

“Inspect records that explain the affected process, then check the result described in this case: An airline concierge sees p95 latency increase during a model refresh” adds a relevant safeguard or verification step rather than weakening the solution. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Question 181

Architecture case: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. What configuration should the engineer choose for this workload?

  1. Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain
  2. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a line-of-business chatbot runs in app service and must call a restricted model deployment without storing credentials in source control
  3. Use a developer personal login token for unattended production calls
  4. Assume network location alone authenticates callers

Explanation

Correct Answer

A:

Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Confirm that the workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied. If the result fails, inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures.

Incorrect Answers

B:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a line-of-business chatbot runs in app service” does not implement the control that the facts call for. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

C:

“Use a developer personal login token for unattended production calls” does not implement the control that the facts call for. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

D:

A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. “Assume network location alone authenticates callers” would not meet the requirement. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

Question 182

Production requirement: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. What technical fact prevents the simplest shortcut from being reliable?

  1. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  2. The fact that the team started work is enough to prove correctness for this exact case: a line-of-business chatbot runs in app service and must call a restricted model deployment without storing credentials in source control
  3. The most powerful or least restricted model is always the safest choice regardless of task conditions
  4. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions

Explanation

Correct Answer

D:

Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

Incorrect Answers

A:

A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. “Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. The implementation must authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

B:

“The fact that the team started work is enough to prove correctness for this exact case: a line-of-business chatbot runs in app service” does not fully explain the decisive technical boundary in this case. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

C:

A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. “The most powerful or least restricted model is always the safest choice regardless of task conditions” does not fully explain the decisive technical boundary in this case. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. The implementation must authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

Question 183

A team is investigating this task: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. What end-to-end test would distinguish successful operation from an installed configuration?

  1. A project dashboard remains green, although the affected request, output and permissions were not checked
  2. The team closes a change ticket without replaying a representative positive and negative test
  3. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied
  4. The operator reports success without reproducing the observed behavior: a line-of-business chatbot runs in app service and must call a restricted model deployment without storing credentials in source control

Explanation

Correct Answer

C:

Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied. If this test fails, inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures.

Incorrect Answers

A:

“A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

B:

Because a line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

D:

“The operator reports success without reproducing the observed behavior: a line-of-business chatbot runs in app service” alone does not establish all the required behavior. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Question 184

Situation: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. Which diagnostic investigation best isolates the issue before another change?

  1. Restart every affected component before collecting request or tool traces
  2. Inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures
  3. Assume the general service is at fault without checking the affected operation in this case: a line-of-business chatbot runs in app service and must call a restricted model deployment without storing credentials in source control
  4. Read only the broad service-health summary and skip actual workload evidence

Explanation

Correct Answer

B:

Because a line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control, inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Incorrect Answers

A:

Because a line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control, “Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures.

C:

“Assume the general service is at fault without checking the affected operation in this case: a line-of-business chatbot runs in app service” would not meet the requirement. Inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures.

D:

Because a line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control, “Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

Question 185

Architecture case: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. Which TWO shortcuts should be rejected for this scenario? Select TWO answers.

  1. Grant all application identities owner access to the entire Azure subscription
  2. Embed administrator API keys in a container image shared across build environments
  3. Inspect records that explain the affected process, then check the result described in this case: A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control
  4. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied
  5. Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain

Explanation

Correct Answer

A:

This grants access or authority beyond the scope established in the case. “Grant all application identities owner access to the entire Azure subscription” would violate the requirement. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

B:

Because a line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control, “Embed administrator API keys in a container image shared across build environments” would violate the requirement. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

Incorrect Answers

C:

“Inspect records that explain the affected process, then check the result described in this case: A line-of-business chatbot runs in App Service” adds a relevant safeguard or verification step rather than weakening the solution. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Confirm that the workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

D:

“The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied” is the required outcome of a working control, not an action that weakens it. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

E:

A line-of-business chatbot runs in App Service and must call a restricted model deployment without storing credentials in source control. “Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain” is the controlled implementation, not an unsafe workaround. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. Confirm that the workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Question 186

Production requirement: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. Which next change most directly addresses the reported technical risk?

  1. Assume network location alone authenticates callers
  2. Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain
  3. Use a developer personal login token for unattended production calls
  4. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in

Explanation

Correct Answer

B:

Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Incorrect Answers

A:

“Assume network location alone authenticates callers” would not meet the requirement. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

C:

“Use a developer personal login token for unattended production calls” does not implement the control that the facts call for. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

D:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a payroll extraction service moved to containers” does not implement the control that the facts call for. Instead, authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

Question 187

A team is investigating this task: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. Which explanation best captures the key behavior of this architecture?

  1. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions
  2. The fact that the team started work is enough to prove correctness for this exact case: a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in
  3. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  4. The most powerful or least restricted model is always the safest choice regardless of task conditions

Explanation

Correct Answer

A:

Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Incorrect Answers

B:

“The fact that the team started work is enough to prove correctness for this exact case: a payroll extraction service moved to containers” would not be the most direct first check for this failure. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

C:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” would not be the most direct first check for this failure. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

D:

“The most powerful or least restricted model is always the safest choice regardless of task conditions” would not be the most direct first check for this failure. Service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

Question 188

Situation: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. Which result would demonstrate that the proposed remedy works end to end?

  1. The team closes a change ticket without replaying a representative positive and negative test
  2. A project dashboard remains green, although the affected request, output and permissions were not checked
  3. The operator reports success without reproducing the observed behavior: a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in
  4. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied

Explanation

Correct Answer

D:

The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Incorrect Answers

A:

Because a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

B:

A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

C:

“The operator reports success without reproducing the observed behavior: a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in” alone does not establish all the required behavior. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Question 189

Architecture case: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. What evidence should the engineer correlate to verify the actual failure cause?

  1. Inspect effective service-principal roles, token audience, tenant, managed-identity assignment, resource scopes and SDK authentication failures
  2. Assume the general service is at fault without checking the affected operation in this case: a payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in
  3. Read only the broad service-health summary and skip actual workload evidence
  4. Restart every affected component before collecting request or tool traces

Explanation

Correct Answer

A:

The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied. If this test fails, service authentication and data authorization are separate checks; possession of a Foundry project URL does not grant deployment or knowledge-store permissions.

Incorrect Answers

B:

“Assume the general service is at fault without checking the affected operation in this case: a payroll extraction service moved to containers” would not meet the requirement. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

C:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

D:

“Restart every affected component before collecting request or tool traces” alone does not establish all the required behavior. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Question 190

Production requirement: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Embed administrator API keys in a container image shared across build environments
  2. Inspect records that explain the affected process, then check the result described in this case: A payroll extraction service moved to containers and experiences authorization failures despite a successful managed identity sign-in
  3. The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied
  4. Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain
  5. Grant all application identities owner access to the entire Azure subscription

Explanation

Correct Answer

A:

“Embed administrator API keys in a container image shared across build environments” would violate the requirement.

E:

This grants access or authority beyond the scope established in the case. “Grant all application identities owner access to the entire Azure subscription” would violate the requirement. The appropriate control instead is to authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain.

Incorrect Answers

B:

“Inspect records that explain the affected process, then check the result described in this case: A payroll extraction service moved to containers” adds a relevant safeguard or verification step rather than weakening the solution. Confirm that the workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

C:

“The workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied” is the required outcome of a working control, not an action that weakens it.

D:

“Authenticate the deployed application with its managed identity, assign narrowly scoped resource roles, and use the supported identity credential chain” is the controlled implementation, not an unsafe workaround. Confirm that the workload can invoke only its intended deployment and search store while a different principal and privileged write requests are denied.

Developing AI Apps and Agents on Azure (AI-103) Practice Tests