Manage, Monitor, and Secure a Microsoft Foundry Service AI-102 Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A third-party vendor needs temporary access to your Foundry service to run a proof-of-concept. You need to grant access that expires automatically and is limited to specific models. What should you use?

   • ACreate a new account key and share it with the vendor, then regenerate the key after the proof-of-concept.
   • BCreate a Microsoft Entra ID guest user account and assign the 'Contributor' role on the Foundry service.
   • CAdd the vendor's IP address to the firewall allowlist and remove it after the proof-of-concept.
   • DCreate a shared access signature (SAS) token with a short expiry and restrict it to the specific model endpoints.
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   Your team runs a Foundry service that processes customer support transcripts. You notice that response latency increases during peak hours, but you are unsure whether the bottleneck is the model endpoint or the downstream database. You need to identify the source of the latency before scaling resources. What should you do first?

   • AEnable Application Insights and configure dependency tracking for the Foundry service, then review end-to-end transaction traces.
   • BIncrease the provisioned capacity of the Foundry service and monitor the average response time over the next week.
   • CExport the Foundry service logs to a storage account and manually correlate timestamps with database slow-query logs.
   • DReview the Azure Monitor metrics for the Foundry service, focusing only on the Requests and Failed Requests counters.
   Reveal Solution Discussion Select an answer first
4. 13expert · medium

   Your organization uses a Microsoft Foundry Service resource for AI workloads. You need to reduce costs, but you also need to maintain a certain level of performance for production workloads. You have identified that development workloads are using a significant portion of the resource and are causing performance degradation for production. What should you do?

   • AUse Azure Cost Management to identify the cost of development workloads and then manually reduce their usage.
   • BImplement rate limiting on the development workloads to reduce their impact.
   • CSet up autoscaling on the Foundry resource to handle peak loads.
   • DMove development workloads to a separate Foundry resource with a lower tier.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   Your Foundry service is used by a real-time inference application that requires low latency. You notice that the service is sometimes throttled during peak hours, causing latency spikes. You have the following constraints: 1) You cannot increase the service's quota due to budget limitations. 2) You need to reduce the number of throttled requests. 3) You need to maintain low latency for critical requests. What should you do?

   • AUse Azure Load Balancer to distribute requests across multiple Foundry service instances.
   • BCache the results of frequent requests in a Redis cache to reduce the number of calls to the Foundry service.
   • CImplement client-side retry logic with exponential backoff to handle throttled requests.
   • DPrioritize critical requests by using a separate endpoint with a higher quota, and move non-critical traffic to a lower-priority endpoint.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   Your organization has a Foundry service that is used by multiple teams. The service is currently using account keys for authentication. A security audit requires that you move to Microsoft Entra ID authentication and that you minimize costs. You have the following constraints: 1) The service must remain available during the migration. 2) You need to track which team is using the most resources. 3) You have a limited budget for the migration. What should you do?

   • AGradually migrate applications to Microsoft Entra ID authentication, keep account keys enabled during the transition, and apply tags for cost tracking.
   • BKeep account keys for now and create a separate Foundry service instance for each team to track costs.
   • CSwitch to Microsoft Entra ID authentication and use Azure Cost Management to allocate costs based on the service's activity logs.
   • DSwitch the service to Microsoft Entra ID authentication, disable account keys, and apply tags to the service for cost tracking.
   Reveal Solution Discussion Select an answer first