6.4 Demonstrate Knowledge of Authentication Failure Resolution (OAuth / PAT) and Webhook Delivery Issues When Connecting Version Control Systems (VCS) (e.g., GitHub, GitLab) and CI/CD Systems (e.g., Jenkins) to Cortex Cloud CLOUD-SECURITY-ENGINEER Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A GitLab PAT used for a Cortex Cloud integration is set to expire in 7 days. The team wants to avoid manual rotation. What is the most appropriate solution?

   • AUse a GitLab deploy token instead of a PAT, as deploy tokens do not expire.
   • BCreate a new PAT with no expiration date and update the integration.
   • CSwitch to OAuth with a refresh token to automatically obtain new access tokens.
   • DUse a service account with a PAT that has a long expiration and set a calendar reminder to rotate it.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A DevOps engineer connects a GitHub organization to Cortex Cloud using OAuth. The initial authorization succeeds, but after 24 hours, the integration stops syncing repositories. The Cortex Cloud logs show 'OAuth token expired' errors. What is the most likely cause and the appropriate resolution?

   • AThe Cortex Cloud app lacks the 'repo' scope; reauthorize with the required scopes.
   • BThe GitHub webhook secret was changed; update the secret in Cortex Cloud to match.
   • CThe OAuth app was installed only for the engineer's personal account; reinstall it for the organization.
   • DThe OAuth access token was issued with a short lifetime; refresh the token or reconfigure the integration to use a refresh token.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   A PAT used for a GitLab integration with Cortex Cloud suddenly stops working. The error message indicates '401 Unauthorized'. What is the most common cause of this failure?

   • AThe PAT has expired or been revoked.
   • BThe GitLab server is down.
   • CThe Cortex Cloud API endpoint has changed.
   • DThe webhook URL is incorrect.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   A Jenkins webhook is not reaching Cortex Cloud. The Jenkins server logs show a 'Connection timed out' error when trying to send the webhook. What is the most likely cause of this issue?

   • AThe webhook URL is incorrect.
   • BThe Cortex Cloud endpoint is not reachable from the Jenkins server due to network connectivity issues.
   • CThe webhook payload is too large.
   • DThe webhook secret is invalid.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   During the OAuth flow to connect Jenkins to Cortex Cloud, the user receives an 'access_denied' error after clicking the authorization link. What does this error typically indicate?

   • AThe OAuth authorization server is temporarily unavailable.
   • BThe OAuth client ID is incorrect.
   • CThe redirect URI is not registered.
   • DThe user declined the authorization request or the OAuth app's requested scopes were not granted.
   Reveal Solution Discussion Select an answer first