Question: What is the purpose of an .env file?
- To keep secret keys outside of source code, which often live in online code repositories
- To set how the environment of the integration is structured
- To configure automated actions in online code repositories
- To host your JSON configurables
Explanation
An .env file is used to keep sensitive configuration values out of source code. In API-based integrations, secrets such as client IDs, client secrets, and token values should not be committed to public or shared repositories. Amazon Ads integrations rely on secure authorization credentials to request access to advertiser resources. Storing those values outside application code reduces the risk of exposing credentials. The file supports environment-specific configuration without hardcoding private values.
Why the other options are incorrect
Environment structure This is incorrect because an .env file stores configuration values, not the overall integration architecture.
Automated actions This is incorrect because repository automation is handled by workflow or CI/CD configuration, not the .env file itself.
JSON configurables This is incorrect because .env files usually store key-value variables, not hosted JSON configuration files.
Source for verification
https://advertising.amazon.com/API/docs/en-us/guides/account-management/authorization/overview
https://developer.amazon.com/docs/login-with-amazon/authorization-code-grant.html
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.