Question: What is the purpose of using OAuth in a one-to-many integration?
- To allow only a single user to authenticate with the integration.
- To allow multiple different users to authenticate with the integration.
- To give multiple users access to the integration indefinitely.
- To allow only super admins access to the integration.
Explanation
OAuth is used when an app needs to be installed and authorized by different users across different accounts. Each user completes an authorization flow that grants the app access based on approved scopes. This supports one-to-many integrations because the same public app can connect to multiple accounts without using one shared private token. The app receives tokens for each authorized account, keeping access separate and permission-based. This model is better suited for distributed integrations than a single-account private app setup.
Why the other options are incorrect
Single user This is incorrect because one-to-many integrations are designed for multiple users or accounts, not one user only.
Indefinite access This is incorrect because OAuth access depends on tokens, scopes, and authorization state, not unlimited permanent access.
Super admins This is incorrect because OAuth authorization is not limited only to super admins by definition.
Source for verification
https://developers.hubspot.com/docs/apps/legacy-apps/authentication/oauth-quickstart-guide
https://developers.hubspot.com/docs/apps/legacy-apps/authentication/intro-to-auth
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.