Explanation: Marketing Cloud authenticates if the user has login hours enabled on their profile when they log in through the user interface3. Login hours are a security feature that allows the admin to specify the time range when users can access Marketing Cloud. If a user tries to log in outside of their login hours, they will be denied access3. The other options are incorrect because:

If the user is assigned a role in the parent business unit. This is not a factor for authentication, but rather for authorization. A role determines what permissions and access levels a user has within Marketing Cloud, but it does not affect their ability to log in through the user interface4.

If the user is logging in from a whitelisted IP address. This is not a factor for authentication, but rather for verification. An IP address whitelist is a list of trusted IP addresses that can access Marketing Cloud without additional verification. If a user logs in from an IP address that is not on the whitelist, they will be asked to verify their identity via email or SMS5.

If the user is an API User on their record. This is not a factor for authentication, but rather for integration. An API User is a user who can access Marketing Cloud via API calls from external applications or systems. This does not affect their ability to log in through the user interface.

Explanation: Data Extension, Audience Studio, API Event, Date Based Event are entry source types for Journey Builder. Entry source types are types of events or data sources that can trigger contacts to enter a journey in Journey Builder. Data Extension is an entry source type that allows contacts from a data extension to enter a journey based on a schedule or an automation. Audience Studio is an entry source type that allows contacts from Audience Studio segments to enter a journey based on a schedule or an automation. API Event is an entry source type that allows contacts to enter a journey based on an API call from an external system or application. Date Based Event is an entry source type that allows contacts from a data extension to enter a journey based on a date field in the data extension, such as birthday or anniversary.

Explanation: There are overlapping contacts in each of the channel is why the total contact count would be less than the total number of contacts from all data sources. Contacts are unique individuals who can be reached through one or more channels in Marketing Cloud, such as email, mobile, or social. Contacts are counted based on their Contact Key, which is a unique identifier for each contact. If a contact has multiple channels associated with them, such as email and mobile, they are only counted once in the total contact count. Therefore, if there are overlapping contacts in each of the channel, the total contact count would be less than the sum of contacts from all data sources.

Explanation:

To ensure Journey Builder directs the subscribers correctly, contact data should be used for the decision split. Contact data is the data that is stored in the contact model and is available for all journeys. Journey data is the data that is captured at the point of entry and is specific to each journey.

Explanation:

Advertising Studio supports lookalike audiences directly from Facebook only. For other networks, such as Google and Twitter, Advertising Studio can create audience segments based on Marketing Cloud data and export them to the network’s platform, where the lookalike audience can be created manually.