Free Salesforce JB-101 Exam Practice Questions & Explanations
Prepared & Reviewed by the ValidExamDumps Editorial Team
At ValidExamDumps, we consistently monitor updates to the Salesforce JB-101 exam questions by Salesforce. Whenever our team identifies changes in the exam questions, objectives, focus areas or requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these up to date and 100% exam domain coverage questions, our customers can successfully pass the Salesforce Journey Builder 101 exam on their first attempt without needing additional materials or study guides.
Other certification materials providers often include outdated or removed questions by Salesforce in their JB-101 exam. These outdated questions lead to customers failing their Salesforce Journey Builder 101 exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions. Our main priority is your success in the Salesforce JB-101 exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.
A B2C client runs an abandoned cart journey with a 24-hour wait followed by a reminder email. They also run a monthly promotional journey. Business rules state that a contact should never receive more than two marketing emails in a 24-hour period, and transactional order confirmations must always be delivered.
How should the consultant configure this in Journey Builder and Email Studio?
Contact Frequency (send limits) is the native capability for enforcing a maximum number of commercial messages per contact over a defined period across journeys and sends. Sends flagged as transactional/operational are excluded from those limits, so order confirmations still deliver.
A is a manual, error-prone workaround requiring continuous list maintenance. B throttles delivery pacing only and does not cap message counts per contact. D controls re-entry into a single journey, not cross-journey message volume, and does not prevent a contact from being in two different journeys.
A consultant is designing a journey where contacts are injected from an Event data extension. Several attributes, such as OrderTotal and OrderDate, exist only on that entry data extension and are needed for personalization in an email sent later in the journey.
The consultant states that these attributes are available as Journey Data throughout the journey without needing any additional data relationship or attribute group configuration.
True. Fields on the entry source data extension are captured as Journey Data at the moment the contact enters and travel with the contact for the life of that journey, so they can be used in personalization, decision splits and filters without additional configuration. Contact Data, by contrast, is looked up in real time via Contact Builder attribute groups and data relationships and reflects the current value at the point of evaluation.
A journey uses a Decision Split to route contacts based on whether they opened the first email. Testing shows that nearly all contacts are taking the default 'Remainder' path even though open tracking shows engagement.
What is the most likely cause?
Engagement-based branching needs time for tracking data to be collected. Without a Wait activity between the send and the split, contacts are evaluated instantly, before opens/clicks occur, so they fall to the Remainder path. Best practice is to insert a wait sized to the expected engagement window.
B is wrong - Decision Splits can use Journey Data, Contact Data and engagement attributes (Engagement Split is simply a purpose-built shortcut). C is unrelated to tracking. D is false; Decision Splits support multiple paths plus a remainder.
A client wants a journey to trigger the moment a customer's loyalty tier changes in a Marketing Cloud data extension, and they want the entry event to fire in near real time rather than on a schedule. Contacts should be able to re-enter each time their tier changes again.
Which configuration best meets this requirement?
An API Event (Event Definition Key + /interaction/v1/events REST call) injects contacts into the journey immediately as the external system detects the tier change, which satisfies the near real-time requirement. Setting 'Re-entry anytime' allows the same contact to be injected again on each subsequent tier change.
A is scheduled, not real time, and 'No Reentry' blocks repeat entries. C listens to Sales/Service Cloud object changes, not a Marketing Cloud data extension, and only fires on Contact creation as described. D refreshes nightly, which is not near real time.
A retailer has a multi-step welcome journey using a Data Extension entry source with a scheduled run every hour. After launch, the marketing team realizes the Wait activity before the second email should be 3 days instead of 1 day, and they want the change applied to contacts entering tomorrow.
What should the consultant advise?
A running journey version's structure (activities, waits, splits) cannot be altered; only a limited set of items such as email send properties can be edited while running. To change a Wait duration you create a new version, make the change, and activate it. Contacts already in the old version continue there, so the old version is typically stopped once no longer needed.
A is wrong because Wait activities are locked in a running version. C is wrong because pausing allows resuming/editing only limited elements and does not permit structural changes to that version. D is invented functionality - reentry mode controls whether contacts can re-enter, not wait durations.