In a Marketing Cloud app integration, what is the Endpoint URL used to load assets and define the base path for resources?

In a Marketing Cloud app integration, what is the Endpoint URL used to load assets and define the base path for resources?

• A. The baseUrl for your application; Journey Builder loads assets relative to this endpoint
• B. The authentication token endpoint
• C. The data export endpoint
• D. The UI path for the custom activity

Answer: (A)

The endpoint URL used to load assets and define the base path for resources is the baseUrl for your application. Journey Builder loads assets such as scripts, images, and configuration files relative to this endpoint, so all resource requests are resolved from that root. This centralized URL keeps asset loading consistent and allows you to host your app wherever you want, as long as the baseUrl is publicly accessible over HTTPS. The other options serve different functions: the authentication token endpoint obtains OAuth tokens, the data export endpoint handles exporting data, and the UI path for the custom activity refers to the app’s internal interface route rather than the root location for assets.

The endpoint URL used to load assets and define the base path for resources is the baseUrl for your application. Journey Builder loads assets such as scripts, images, and configuration files relative to this endpoint, so all resource requests are resolved from that root. This centralized URL keeps asset loading consistent and allows you to host your app wherever you want, as long as the baseUrl is publicly accessible over HTTPS. The other options serve different functions: the authentication token endpoint obtains OAuth tokens, the data export endpoint handles exporting data, and the UI path for the custom activity refers to the app’s internal interface route rather than the root location for assets.