
Ultimate access to all questions.
A developer creates an app using Amazon API Gateway with access limited to the Sales department via Amazon Cognito and a Lambda authorizer. Despite updating their IdP attribute to Sales, the developer is denied access due to the access token still showing Engineering. What could cause this discrepancy?
A
The Lambda authorizer's authorization caching might be using an outdated policy based on the previous Engineering attribute.
B
Caching on the Amazon Cognito user pool could be involved, but this is less likely the direct cause of the department value issue.
C
A missing Department tag on the Lambda authorizer's IAM role might affect access control but isn't the main reason for the incorrect department reporting.
D
A missing Department tag on the Amazon Cognito user pool's IAM role isn't the primary cause of the caching issue with the user's department attribute.