Question: When expiring your private app access tokens, how much of a time buffer can you set before the private app token is rotated?
- Three days
- Five days
- Seven days
- Nine days
Explanation
The rotation buffer gives time to replace the old private app access token before it stops working. HubSpot’s rotation flow can create a new token while the existing token remains temporarily valid. Choosing “rotate and expire later” triggers expiration of the old token after seven days. This buffer helps prevent integration downtime while the new token is added to the connected system. Token rotation should be handled securely because the token authorizes API access.
Why the other options are incorrect
Three days This is incorrect because HubSpot’s delayed expiration buffer is longer than three days.
Five days This is incorrect because five days is not the delayed expiration period used for private app token rotation.
Nine days This is incorrect because the token rotation buffer is not nine days.
Source for verification
https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview
The answer(s) to the question is highlighted in the BOLD text above. You can also find more questions and answers related to the exams on the "Integrating With HubSpot I: Foundations" page.