Question: Which of the following is NOT a benefit of using OAuth as your authentication flow?
- It adds more complexity to the integration’s authentication.
- It allows an application to be portable.
- It can be created inside of single HubSpot accounts.
- It allows you to list your integration on the App Marketplace.
Explanation
Creating an app inside a single HubSpot account describes a private app pattern, not an OAuth-based public app pattern. OAuth is used when an integration needs to be authorized by different users across different HubSpot accounts. This makes the app portable because each account can grant access through its own authorization flow. OAuth is also required for apps intended for the App Marketplace. The added authentication complexity is a tradeoff, not the incorrect benefit.
Why the other options are incorrect
Complexity This is a real consideration because OAuth adds more setup compared with a single private app token.
Portable This is a valid benefit because OAuth allows the same app to connect with multiple HubSpot accounts.
App Marketplace This is a valid benefit because Marketplace apps use OAuth for account authorization.
Source for verification
https://developers.hubspot.com/docs/apps/legacy-apps/authentication/oauth-quickstart-guide
https://developers.hubspot.com/docs/apps/marketplace/app-certification-requirements
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.