1Z0-340-25 Sample Questions & Answers

Eloqua's lead scoring model allows you to configure criteria for both profile (explicit data like job title) and engagement (implicit data like web visits) within the same model. This is where the points are assigned.

After the scores are calculated in the model, a separate mapping is required to translate the numeric scores into the alphanumeric rating. For example, a profile score of 80-100 is an 'A', and an engagement score of 50-75 is a '2', resulting in a combined rating of 'A2'.

The 'Campaign Activation' permission specifically controls a user's ability to activate campaigns, which includes sending emails through the campaign canvas or via single-batch sends. Denying this permission while allowing asset creation permissions (like 'Email-Create' and 'Landing Page-Create') will achieve the desired level of access for the intern.

When writing to a CDO from a form, the processing step needs a key field to either create a new record or update an existing one. Typically, the contact's email address is used to map the form submission to a CDO record. If this unique identifier is not mapped in the processing step's configuration, Eloqua does not know how to link the data, and the CDO record will not be created or updated.

For Eloqua to attribute revenue from a Salesforce Opportunity, it needs to link the campaign to the opportunity. This is done via Campaign Responses. In Eloqua, you must define and enable response rules within the campaign settings (e.g., a form submission or email click counts as a response). When these responses are synced to the Salesforce Campaign, they associate the contact with that campaign. Salesforce then uses its own attribution logic (often via Contact Roles on the Opportunity) to link that campaign member to a closed-won Opportunity, and this revenue data is synced back to Eloqua. Without the initial response rule being triggered and synced, the chain of attribution is broken.

First-party cookies are the modern standard for tracking and are essential for cross-subdomain tracking. By setting the cookie domain to the top-level domain (e.g., .university.edu), the cookie becomes accessible to all its subdomains (www.university.edu, apply.university.edu, etc.). This allows Eloqua to recognize the visitor as the same person across their entire journey on the university's web properties.

Eloqua processes segment filters sequentially. The most effective optimization technique is to place the filter that will exclude the largest number of contacts at the very beginning of the criteria list. This drastically reduces the dataset that subsequent, more complex filters (like checks against linked accounts or shared lists) need to process, leading to a significant improvement in calculation speed. For example, filtering by 'Email Address is not empty' first is more efficient than checking against a shared list first.

Eloqua does not have a native, built-in SMS sending capability. This functionality is enabled by integrating with third-party SMS providers. The first step is to select a provider, then install and configure their specific app (connector) from the Oracle App Cloud. This app provides the necessary cloud action or decision services that can be used on the campaign or program canvas to send the SMS messages.

This accurately describes the standard Eloqua data model. The Account object is the parent, and multiple Contact records can be linked to a single Account (a one-to-many relationship). The Contact is the central entity for marketing. Custom Data Objects are used to store additional, often transactional or event-related, data. A single Contact (identified by a unique key like email address) can be linked to many records within a CDO, representing, for example, multiple event attendances or product purchases.

Eloqua Engage is designed to honor the core deliverability settings automatically, such as master unsubscribes and contacts who have hard bounced. However, for more granular control, such as respecting unsubscribes from specific Email Groups (e.g., 'Newsletter') or custom suppression lists (e.g., 'Competitors'), an administrator must explicitly configure these options within the global Engage settings. This ensures that sales reps using Engage adhere to the same communication rules as automated marketing campaigns.

The Campaign Canvas is primarily for orchestrating a sequence of marketing communications (emails, form submissions, etc.) to a specific audience over a defined period. The Program Canvas is an always-on utility that is ideal for data management tasks (like lead scoring or data washing) and for complex, long-term lead nurturing where contacts can enter and exit based on evolving criteria rather than a fixed campaign timeline.