A marketer reports that clicks on the main image in an email are not being tracked. What are two possible reasons for this? (Choose two.)
Correct Answer: B,C
Explanation Two possible reasons why clicks on the main image in an email are not being tracked are: * The "Click Tracking for email" option is disabled for the email. This option is a global setting that enables or disables click tracking for all the links in an email. If this option is disabled, none of the links in the email will be tracked, including the main image link. The developer can enable this option in the Email Configuration menu under Tracking Settings. * The Tracking Type on the link is set to "Never". This option is a link-specific setting that defines how a link should be tracked in an email. There are three possible values for this option: Always, Never, or Default. If this option is set to Never, the link will not be tracked, regardless of the global setting. The developer can change this option in the Link Properties menu under Tracking Type. The other options are not valid or relevant reasons why clicks on the main image in an email are not being tracked. The "Open Tracking for email" option is a global setting that enables or disables open tracking for an email, which measures how many times an email is opened by recipients. This option does not affect click tracking for links in an email. Link tracking is enabled by default for all links in an email, unless they are explicitly disabled by the global or link-specific settings. Therefore, having no Label on a link does not prevent it from being tracked. References: https://experienceleague.adobe.com/docs/journey-optimizer/using/email-channel/configure-email-channel. https://experienceleague.adobe.com/docs/journey-optimizer/using/email-channel/design-your-email-conten
Question 7
A Marketer wants to develop a journey where the recipients should be targeted in their time zones. How can this journey be configured to fulfill this requirement?
Correct Answer: A
Explanation To configure a journey where the recipients should be targeted in their time zones, the developer should enable "Use profile time zone in waits and conditions" in journey properties. This is a journey property that defines whether customers should be evaluated or processed based on their own time zone or based on the default time zone of the journey. If this property is enabled, customers will be targeted in their time zones for any waits or conditions that involve date or time criteria or expressions. For example, if a wait activity is configured to wait until 9 AM, customers will receive the next activity at 9 AM in their own time zone, not in the default time zone of the journey. The other options are not valid or existing ways to configure a journey where the recipients should be targeted in their time zones. There is no option to select time zone from user profile or enable profile time zones in configurations. References: https://experienceleague.adobe.com/docs/journey-optimizer/using/journeys/create-a-journey.html?lang=en#journ
Question 8
A developer needs to add new customer attributes to be used for a new marketing program to their existing customer schema. What is a possible way to extend the existing schema within the Experience Data Model?
Correct Answer: A
Explanation To add new customer attributes to an existing customer schema, the developer can simply add a new field to the schema using the Schema Editor UI or the Schema Registry API. A field is a basic unit of data that describes an attribute of an entity, such as name, email, or loyalty level. The developer can specify the field name, data type, description, and other properties for the new field. The developer does not need to extend the class with a new field or create a new class with the new field, as these are not valid or necessary options for this use case. A class is a predefined structure that defines the type and semantics of an entity, such as profile or event. A class cannot be extended with a new field, but it can be mixed with other classes or mixins to add more fields. A new class does not need to be created for adding new customer attributes, as they can be added to the existing customer schema. References: https://experienceleague.adobe.com/docs/experience-platform/xdm/tutorials/create-schema-ui.html?lang=enhttps
Question 9
An Adobe Journey Optimizer developer wants to copy a Schema created in a development sandbox to production sandbox. Which feature in AEP can be used to achieve this?
Correct Answer: B
Explanation To copy a Schema created in a development sandbox to production sandbox, the developer can use the Export/Import Schema Package feature in AEP. This feature allows the developer to export a Schema and its dependencies, such as field groups, data types, and mixins, as a package file that can be imported into another sandbox. The Export/Import Sandbox API is not a valid option, as it is used to export or import an entire sandbox configuration, not a specific Schema. The Export/Import Schema API is also not a valid option, as it is used to export or import a single Schema without its dependencies, which may cause errors or inconsistencies. References: https://experienceleague.adobe.com/docs/experience-platform/xdm/tutorials/export-import-schema-package.htm https://experienceleague.adobe.com/docs/experience-platform/sandbox/api/export-import-sandbox.html?lang=en
Question 10
The dimensional entity that exists within the Real-Time Customer Profile data store (also sometimes referred to as lookup or classification schemas) is primarily used for what two purposes? (Choose two.)
Correct Answer: A,B
Explanation A dimensional entity is a type of entity that exists within the Real-Time Customer Profile data store and describes a business entity or concept that is not directly related to a customer, such as product, location, or campaign. A dimensional entity is primarily used for two purposes: * It helps simplify the modeling process in XDM by avoiding having to restate common data on either the event or the traits of a profile. For example, instead of repeating the product name, price, and description on every product view event, the developer can create a product dimensional entity and reference it by its ID on the event. * It allows Journey Optimizer to leverage the data for audience and segment qualification initiated customer journeys. For example, the developer can create a segment based on customers who viewed products from a certain category or location, or who interacted with a certain campaign. The other options are not valid or relevant purposes of a dimensional entity. A dimensional entity is not leveraged during batch segmentation jobs that are run within the Real-Time Customer Profile, as these jobs are based on profile data, not dimensional data. A dimensional entity does not ensure that data is optimally stored to deliver real-time experiences and segmentation, as this is a function of the Real-Time Customer Profile data store, not the dimensional entity itself. References: https://experienceleague.adobe.com/docs/experience-platform/profile/home.html?lang=en#dimensional-en https://experienceleague.adobe.com/docs/journey-optimizer/using/get-started/data-ingestion.html?lang=en
