I’m a bit confused about option C. Adding the field to the search layout sounds good, but making it required for Customer Support Reps seems off since they shouldn't be editing it.
I feel like we had a practice question that was similar to this, and it focused on how to manage user permissions effectively. I think B aligns with that concept.
I'm not entirely sure, but I think validation rules are more about enforcing data integrity rather than controlling visibility. So, option A might not be the best fit here.
I remember we discussed field-level security in class, and it seems like option B might be the right choice since it controls visibility and editability based on profiles.
This one seems straightforward to me. If the API Gateway is caching the POST requests, that could be causing the issue, even if the Lambda function is working correctly. I'd try disabling caching on the POST API and see if that resolves the problem.
I'm confident I can solve this one. The Consumption plan is the best choice to minimize costs and scale automatically. And the Azure Blob Storage trigger will ensure the images are processed quickly.
Tequila
3 months agoLorrine
3 months agoGilberto
4 months agoTashia
4 months agoTiara
4 months agoLorrie
4 months agoProvidencia
4 months agoTamar
5 months agoFrancene
5 months agoJess
5 months agoRolland
5 months agoAdela
5 months agoFrance
5 months agoMel
5 months ago