Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 8 of 107
Free Preview · 107 of 355 · questions 1–107 of 355 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
When Cloud Identity-Aware Proxy (IAP) is used, it adds a special JWT token (assertion) to each request in the Authorization: Bearer <token> header. To ensure that the request actually came through IAP (and not directly), your application must validate this JWT token. This is the only way to guarantee that the request went through IAP and was not sent bypassing it. Google Cloud: Verifying IAP JWT tokens https://docs.cloud.google.com/iap/docs/signed-headers-howto
Answer is A.
Cloud Identity-Aware Proxy (IAP) and Identity Headers: When IAP intercepts a request to your ERP system, it adds special identity headers to the HTTP request. These headers contain information about the authenticated user, such as their email address and group memberships. Validating Headers: Your ERP system needs to be configured to read and validate these identity headers. This allows the ERP system to: Confirm the user's identity: Verify that the user has been authenticated by IAP. Enforce authorization: Use the information in the headers (like group membership) to determine what the user is allowed to do within the ERP system. Why other options are incorrect: A. JWT Assertion: While IAP can use JWTs, it primarily relies on identity headers for this type of authentication.