How should you add custom Journey Builder events or activities to an existing Marketing Cloud app?

• A. Add them as components in the same installed package
• B. Add them as separate, new packages
• C. Publish them directly to AppExchange
• D. Expose them via a public API endpoint

Answer: (A)

Custom Journey Builder events or activities live as components inside the installed package for your Marketing Cloud app. Keeping them in the same installed package ensures a single deployment unit, so you can manage versioning, permissions, and lifecycle together, and they’ll be registered and visible in Journey Builder for that account once the package is installed. Using separate new packages adds unnecessary packaging complexity and makes updates and environment migrations more difficult. Publishing to AppExchange is for distributing apps to customers, not for adding new activities to an existing app in your own account. Exposing a public API endpoint is about how the activity communicates with external systems, not the mechanism for adding the activity itself; the packaging inside the same installed package is what makes the activity available in Journey Builder.