I85PREP
⌘ K
Adobe Journey Optimizer Developer Expert study materials
Adobe Journey Optimizer Developer Expert study resources

Adobe Journey Optimizer Developer Expert practice questions

One question at a time. Build your Adobe Journey Optimizer Developer Expert understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Journey Orchestration

Which journey type in Adobe Journey Optimizer is triggered in real time by a business event such as an abandoned cart or a shipment update?

  1. Audience-triggered journey
  2. Event-triggered journey Correct answer.
  3. Scheduled read-audience journey
  4. Business event journey

Explanation

Event-triggered journeys start when an inbound event is received for a profile, so each entry is processed individually in near real time. Audience-triggered journeys instead start from a batch audience evaluation.

Question 2Journey Orchestration

In a journey canvas, which node type is used to branch the path based on profile attributes or context data evaluated at that point in the journey?

  1. Wait node
  2. Action node
  3. Event node
  4. Condition node Correct answer.

Explanation

A condition node evaluates expressions against the profile or journey context and routes each profile down the matching branch. Wait nodes only pause timing, and action nodes deliver messages.

Question 3Journey Orchestration

A developer needs a journey to pause each profile for three days after a welcome email before sending a follow-up. Which configuration achieves this?

  1. Add a condition node that checks the profile's last contact date
  2. Set the journey's time zone to a three-day offset
  3. Set the journey re-entrance rule to three days
  4. Add a wait node configured with a fixed duration of three days Correct answer.

Explanation

A wait node with a duration holds each profile on the path for the specified time before advancing to the next node. Re-entrance rules control whether a profile can start the journey again, not in-journey timing.

Question 4Journey Orchestration

Which journey property controls whether the same profile can start a journey more than once?

  1. Journey schedule
  2. Re-entrance rule Correct answer.
  3. Exit condition
  4. Entrance audience

Explanation

The re-entrance rule determines whether a profile may enter the journey again and, if allowed, after what period. Exit conditions instead remove profiles already in the journey.

Question 5Journey Orchestration

What is the purpose of a journey exit condition?

  1. To define the audience that starts the journey
  2. To schedule when the journey becomes live
  3. To limit the number of times a profile can enter
  4. To remove profiles from the journey when a specified criterion is met Correct answer.

Explanation

Exit conditions are evaluated while profiles are active in the journey and remove them when the condition becomes true, such as a purchase completing an abandoned-cart flow. Entry audiences and re-entrance rules affect a different phase of the lifecycle.

Question 6Journey Orchestration

Which statement describes the journey live report in Adobe Journey Optimizer?

  1. It stores the raw event payloads received by the journey
  2. It shows aggregated metrics such as profiles entered and messages delivered for a published journey Correct answer.
  3. It configures the channel surfaces used by journey actions
  4. It lists all unpublished draft journeys and their validation warnings

Explanation

The live report presents near-real-time performance metrics for a running journey, including entry counts and delivery outcomes. Draft validation, raw payload storage, and channel surface configuration are handled elsewhere.

Question 7Journey Orchestration

Which element must be defined before an event-triggered journey can reference an inbound event as its entry source?

  1. A channel surface configuration
  2. A frequency capping rule
  3. An event schema in the journey event configuration Correct answer.
  4. A send-time optimization configuration

Explanation

Events used to trigger journeys are defined with a schema that describes the payload, and the journey references that event definition. Channel surfaces and optimization settings are irrelevant to event entry.

Question 8Journey Orchestration

In a journey, what does the profile time zone setting affect?

  1. The schema used to validate incoming events
  2. The evaluation of time-based waits and time-of-day conditions relative to each profile Correct answer.
  3. The number of profiles allowed to enter per hour
  4. The channel used for the journey's messages

Explanation

When a journey uses the profile time zone, time-based logic such as waits and time conditions is evaluated in each profile's local time zone. It does not affect event schemas, throughput limits, or channel selection.

Question 9Journey Orchestration

A marketer wants profiles who enter a loyalty audience to receive a message, but the journey must run once daily at a fixed hour. Which journey type should be used?

  1. Event-triggered journey
  2. Read-audience journey with a daily schedule Correct answer.
  3. Business event journey
  4. Unitary journey triggered by an API call

Explanation

A read-audience journey evaluates an audience on a schedule and processes qualifying profiles at each run. Event-triggered journeys fire on individual inbound events rather than a fixed daily cadence.

Question 10Journey Orchestration

A developer needs to send an SMS only if a profile has opted in to SMS and otherwise send an email. Which design implements this cleanly?

  1. An event node placed before the SMS action
  2. Two separate journeys with the same audience
  3. A single SMS action node with a fallback channel setting
  4. A condition node that branches on the opt-in attribute, with an SMS action on one branch and an email action on the other Correct answer.

Explanation

A condition node evaluates the opt-in attribute and routes profiles to the appropriate channel action. This keeps the logic in one journey and guarantees exactly one channel path per profile.

Question 11Journey Orchestration

Which configuration ensures that a profile who has already completed a purchase does not receive a reminder email later in an abandoned-cart journey?

  1. Increase the wait duration
  2. Reduce the re-entrance period
  3. Add a second entrance audience
  4. Add an exit condition based on the purchase event or order attribute Correct answer.

Explanation

Exit conditions remove active profiles when the criterion is satisfied, so a purchase stops further reminders. Waits and re-entrance settings do not react to the purchase itself.

Question 12Journey Orchestration

A journey action must call an external system to reserve inventory before sending a confirmation. Which capability should be used?

  1. A wait node with a duration
  2. A custom action configured with an external data source Correct answer.
  3. A journey exit condition
  4. A condition node with a profile attribute

Explanation

Custom actions let a journey call external systems through a configured data source and request, enabling integration steps such as inventory reservation. Wait, condition, and exit nodes do not perform outbound calls.

Question 13Journey Orchestration

Which statement accurately describes how Adobe Journey Optimizer handles a profile that is already in a journey when a new version is published?

  1. Profiles continue on the version they entered unless the journey is stopped and republished Correct answer.
  2. Active profiles are removed and must re-enter the journey
  3. All active profiles are immediately restarted on the new version
  4. The new version applies only to profiles in the entrance audience

Explanation

Publishing an updated journey does not retroactively move in-flight profiles; they continue on the version they entered. Only a stop and republish forces active profiles to be handled under the new configuration.

Question 14Journey Orchestration

What is the role of the journey's entrance audience for an audience-triggered journey?

  1. It specifies the channel surfaces available to the journey
  2. It defines the message content sent by action nodes
  3. It controls the maximum number of messages per profile
  4. It defines which profiles qualify to enter when the journey runs Correct answer.

Explanation

The entrance audience determines the set of profiles evaluated for entry when an audience-triggered journey runs. Content, capping, and channel surfaces are configured separately.

Question 15Journey Orchestration

A developer wants to test a journey with a small set of profiles before full rollout. Which approach best supports this?

  1. Remove the re-entrance rule
  2. Disable the exit condition temporarily
  3. Use test mode or a test profile to simulate the journey path Correct answer.
  4. Publish the journey to production and monitor the live report

Explanation

Test mode and test profiles let a developer simulate journey execution and inspect the path without delivering to the full audience. Publishing to production exposes real profiles and is not a controlled test.

Question 16Journey Orchestration

Which expression context is typically used inside a journey action to personalize content with data captured by the triggering event?

  1. The journey's schedule configuration
  2. The channel surface settings
  3. The re-entrance rule definition
  4. The event context containing the event payload fields Correct answer.

Explanation

Event payload fields are available in the journey context so actions can reference them for personalization. Schedule, surface, and re-entrance settings do not carry event data.

Question 17Journey Orchestration

A journey has a condition node with two branches that later rejoin at a shared action. What happens to a profile that takes the first branch?

  1. It follows only its matching branch and then continues to the shared action Correct answer.
  2. It executes both branches before reaching the shared action
  3. It is duplicated so each branch delivers the shared action
  4. It exits the journey at the condition node

Explanation

A condition node routes each profile down exactly one matching branch, and paths can converge so the profile continues to the shared downstream node once. Profiles are not duplicated across branches.

Question 18Journey Orchestration

Which setting determines when an audience-triggered journey begins processing profiles after publication?

  1. The journey's schedule configuration Correct answer.
  2. The exit condition
  3. The channel surface
  4. The re-entrance rule

Explanation

The schedule defines the start date and recurrence for audience-triggered journeys, so it controls when profiles are processed after publication. Re-entrance, exit conditions, and surfaces serve different purposes.

Question 19Journey Orchestration

A developer observes that profiles are entering an event-triggered journey multiple times in quick succession for the same order. Which configuration most directly prevents this?

  1. Increase the journey's execution frequency
  2. Set the re-entrance rule to disallow re-entry or require a delay Correct answer.
  3. Add a condition node that checks the order ID
  4. Add a wait node after the entry event

Explanation

The re-entrance rule controls whether and how soon a profile may start the journey again, which directly limits duplicate entries from repeated events. A condition node can filter content but does not by itself prevent re-entry.

Question 20Journey Orchestration

A journey must send a message at 9 a.m. in each profile's local time. Which configuration combination achieves this?

  1. A condition node comparing the profile's country to a fixed value
  2. A wait node until a specific time of day combined with the profile time zone setting Correct answer.
  3. A wait node with a fixed duration and no time zone setting
  4. An exit condition based on the current time

Explanation

Waiting until a specific time of day, evaluated with the profile time zone, delivers at 9 a.m. local time for each profile. A fixed duration does not align to a clock time across time zones.

Question 21Journey Orchestration

A custom action in a journey fails intermittently when the external endpoint is slow. Which design consideration best improves resilience?

  1. Configure appropriate timeout and retry behavior for the custom action Correct answer.
  2. Add a condition node before the custom action
  3. Remove the custom action and rely on an email
  4. Shorten the journey's wait durations

Explanation

Custom actions support timeout and retry configuration so transient external failures can be tolerated. Removing the integration or adding a condition does not address endpoint latency.

Question 22Journey Orchestration

An audience-triggered journey is configured to process profiles daily, but a profile qualifies for the audience and then stops qualifying before the next run. What is the expected behavior?

  1. The profile is processed only after re-entering the audience
  2. The profile is processed only if it qualifies at the time the journey run evaluates the audience Correct answer.
  3. The profile is processed twice to compensate
  4. The profile is processed because it qualified at any point

Explanation

Scheduled audience journeys evaluate audience membership at run time, so profiles must qualify when the run occurs. Qualification between runs does not guarantee processing.

Question 23Journey Orchestration

A developer needs to branch on a computed value that combines event data and profile data. Where should this logic be implemented?

  1. In the journey's exit condition
  2. In the channel surface configuration
  3. In a condition node expression that references both event context and profile attributes Correct answer.
  4. In the re-entrance rule

Explanation

Condition node expressions can combine event context fields with profile attributes to compute a branching decision. Surfaces, re-entrance, and exit conditions do not evaluate combined expressions for branching.

Question 24Journey Orchestration

Which statement best describes how journey reporting reflects profiles that exit early via an exit condition?

  1. They are removed from all reporting history
  2. They are reflected as exited profiles and are not counted as completing downstream actions Correct answer.
  3. They are counted as delivered messages regardless of exit
  4. They are automatically re-entered at the next run

Explanation

Profiles removed by an exit condition are recorded as exited and do not proceed to downstream actions, so those actions are not counted for them. Reporting retains the history rather than discarding it.

Question 25Journey Orchestration

Which node type is required to bring an inbound event into the middle of an already-running journey rather than at entry?

  1. An event node placed on the path after entry Correct answer.
  2. An action node
  3. A wait node
  4. A condition node

Explanation

An event node on the journey path listens for an inbound event after entry, allowing the journey to react to later activity such as a purchase. Wait, action, and condition nodes do not listen for events.

Question 26Journey Orchestration

Which journey type begins processing profiles as soon as they qualify for an associated segment?

  1. Read audience journey
  2. Audience-triggered journey Correct answer.
  3. Business event journey
  4. Event-triggered journey

Explanation

An audience-triggered journey listens to segment membership changes and admits profiles when they enter the segment, subject to the configured processing cadence. Event-triggered journeys instead react to a received experience event. Read audience journeys are a legacy pattern that re-evaluates the whole segment on a schedule.

Question 27Journey Orchestration

Which node type ends a profile's path in a journey without sending a message?

  1. Wait node
  2. End node Correct answer.
  3. Timeout node
  4. Condition node

Explanation

An end node explicitly terminates the path for a profile and can be used where a branch should stop. Wait and timeout nodes control timing rather than terminating the path, and condition nodes route profiles to subsequent branches.

Question 28Journey Orchestration

What does a wait node with a fixed duration do to a profile in a journey?

  1. It delays only message delivery while the profile advances through later nodes.
  2. It holds the profile on that path until the duration elapses, then continues to the next node. Correct answer.
  3. It removes the profile from the journey for the duration and re-admits it afterward.
  4. It pauses the entire journey for all profiles for the configured duration.

Explanation

A fixed-duration wait node suspends the individual profile's path for the specified period and then resumes downstream processing. It is scoped to that profile's path, so other profiles and other branches continue unaffected.

Question 29Journey Orchestration

Which journey property defines the maximum time a profile may spend in the journey before being exited automatically?

  1. Re-entrance rule
  2. Exit criteria
  3. Entrance audience
  4. Journey timeout Correct answer.

Explanation

A journey timeout sets the overall maximum duration a profile may remain in the journey, after which the profile is exited automatically. Exit criteria define conditions that remove a profile early, and re-entrance rules govern repeat entry.

Question 30Journey Orchestration

Which statement describes the purpose of a condition node in a journey?

  1. It sends a personalized message to a profile.
  2. It evaluates criteria and routes each profile down one of two branches. Correct answer.
  3. It waits until a specified date and time before continuing.
  4. It merges two branches back into a single path.

Explanation

A condition node tests a rule or expression and directs the profile to the true or false branch accordingly. Branch merging and message delivery are handled by other node types.

Question 31Journey Orchestration

Which capability allows a journey action to send data to a non-Adobe system such as an internal reservation service?

  1. Journey event
  2. Audience qualification
  3. Built-in message action
  4. Custom action Correct answer.

Explanation

A custom action defines an outbound call to an external endpoint, typically configured with a request payload and response handling. Built-in message actions target Adobe delivery channels rather than arbitrary third-party endpoints.

Question 32Journey Orchestration

What is the effect of publishing a journey?

  1. It makes the journey live so that eligible profiles can begin entering and processing. Correct answer.
  2. It creates a draft copy that must be published again before profiles can enter.
  3. It archives the previous version and deletes all prior reports.
  4. It locks the journey so that no further versions can ever be created.

Explanation

Publishing activates the journey so that eligible profiles are admitted and processed according to its configuration. Drafts are separate working copies, and versioning remains available after publication.

Question 33Journey Orchestration

Which item must exist before an action node can reference a named data source in a journey?

  1. A configured data source Correct answer.
  2. A test profile
  3. A journey version
  4. A published segment

Explanation

Named data sources must be configured in the journey environment before nodes can look up data from them. Segments, test profiles, and versions are unrelated to defining a lookup source.

Question 34Journey Orchestration

A marketer wants profiles to pause for three days after a welcome email and then receive a follow-up. Which configuration implements this directly?

  1. A wait node set to a duration of three days placed after the email action. Correct answer.
  2. An exit criterion that removes profiles for three days.
  3. A journey timeout of three days applied to the whole journey.
  4. A condition node that checks whether three days have elapsed.

Explanation

A duration-based wait node placed between the two actions holds each profile's path for three days before the follow-up runs. A journey timeout would exit profiles rather than resume them, and conditions do not themselves delay processing.

Question 35Journey Orchestration

A developer wants a journey to admit a profile only once, even if the profile later qualifies again. Which setting enforces this?

  1. Disabling re-entrance for the journey Correct answer.
  2. Adding an exit condition
  3. Setting a journey timeout
  4. Configuring a frequency cap on the action

Explanation

Re-entrance settings control whether a profile that has already been through the journey may enter again. Disallowing re-entrance ensures a single admission per profile. Timeouts, exit conditions, and action frequency caps affect duration or delivery, not repeat admission.

Question 36Journey Orchestration

A developer needs to route profiles to different actions based on whether a profile's loyalty tier equals gold. Where should this decision be made?

  1. In the journey timeout configuration
  2. In the re-entrance rule of the journey
  3. In the entrance audience definition only
  4. In a condition node placed before the actions Correct answer.

Explanation

A condition node evaluates profile attributes and routes each profile to the appropriate branch, so tier-based routing belongs there. Audience definitions control admission, and the other settings govern repeat entry or duration.

Question 37Journey Orchestration

A developer wants to validate a journey's logic with a small number of known profiles before going live. Which approach fits best?

  1. Disabling re-entrance so profiles can enter only once.
  2. Configuring a very short journey timeout to limit exposure.
  3. Publishing the journey and monitoring the live report for anomalies.
  4. Creating a test mode run against selected profiles in the journey canvas. Correct answer.

Explanation

Test mode lets a developer send selected profiles through the journey to observe path behavior and message rendering without exposing the full audience. Publishing to production or shortening timeouts does not provide controlled validation.

Question 38Journey Orchestration

A developer must ensure that profiles who make a purchase stop receiving reminder messages in an active journey. Which configuration achieves this?

  1. A condition node after each reminder action
  2. A higher frequency cap on the message action
  3. A longer wait before each reminder
  4. An exit condition based on the purchase event Correct answer.

Explanation

An exit condition is evaluated while profiles are in the journey and removes them when the specified event or criteria occur, so a purchase-based exit condition stops further reminders. Conditions placed after actions only act once the profile reaches them.

Question 39Journey Orchestration

A developer needs a journey to look up a profile's account balance from an external system at a decision point. Which journey component provides this?

  1. An entrance audience
  2. A wait node with a duration
  3. A custom action with a response payload Correct answer.
  4. A journey timeout

Explanation

A custom action can call an external endpoint and capture the response, making the returned data available for subsequent logic. Wait nodes, audiences, and timeouts do not retrieve external data.

Question 40Journey Orchestration

A developer wants to compute a combined score from event data and profile attributes and branch on it. Where should this logic live?

  1. In the journey's re-entrance rule
  2. In the message action's send time setting
  3. In the entrance audience definition
  4. In a condition node expression that references both sources Correct answer.

Explanation

Condition node expressions can reference the journey context, including event data and profile attributes, so combined logic belongs in the condition. Audience definitions filter admission, and the other settings do not evaluate arbitrary expressions.

Question 41Journey Orchestration

A profile enters an event-triggered journey and passes a condition node whose true branch leads to an action that is also reached by the false branch. What happens to the profile?

  1. The profile is duplicated and receives the action twice.
  2. The profile waits at the condition until both branches complete.
  3. The profile follows only one branch and reaches the shared action once. Correct answer.
  4. The profile is blocked because branches cannot converge.

Explanation

Each profile traverses a single branch based on the condition result, and branches may route to the same downstream node. The profile therefore arrives at the shared action once, not once per branch.

Question 42Journey Orchestration

A developer needs to send a message only if a profile has consented to a channel, and otherwise route to an alternate action. Which node should perform the check?

  1. A wait node
  2. An end node
  3. A condition node Correct answer.
  4. A journey timeout

Explanation

A condition node evaluates the consent attribute and routes the profile to the appropriate branch, enabling a compliant alternative path. Wait and end nodes do not evaluate criteria, and a timeout only limits duration.

Question 43Journey Orchestration

Which statement describes how a business event differs from an experience event as a journey trigger?

  1. A business event can only be raised by a profile's web interaction.
  2. A business event represents a non-profile-centric occurrence such as an inventory alert. Correct answer.
  3. A business event is identical to an experience event in all respects.
  4. A business event requires segment membership before it can fire.

Explanation

Business events model occurrences that are not tied to a single profile's interaction, such as a stock threshold or price change. Experience events typically represent profile actions, and business events do not require segment membership.

Question 44Journey Orchestration

A developer wants a journey to admit profiles from a segment on a recurring schedule rather than continuously. Which journey configuration supports this?

  1. An event-triggered journey with a wait node
  2. A business event journey with a timeout
  3. A read audience journey with a defined schedule Correct answer.
  4. An audience-triggered journey with re-entrance disabled

Explanation

A read audience journey evaluates the segment on a defined recurring schedule and admits qualifying profiles at each run. Disabling re-entrance does not change the processing cadence of an audience-triggered journey.

Question 45Journey Orchestration

A developer observes that a custom action sometimes fails when the external endpoint responds slowly. Which design consideration best improves resilience?

  1. Remove the custom action and rely on a wait node instead.
  2. Configure a timeout and failure path on the action so profiles continue through an alternate branch. Correct answer.
  3. Disable re-entrance so profiles cannot retry the journey.
  4. Increase the journey timeout to the maximum allowed value.

Explanation

Action-level timeout and failure handling route profiles to an alternate path when the external call does not succeed, preventing stalled journeys. The other options either remove needed functionality or do not address the failure.

Question 46Journey Orchestration

A developer needs to branch on a value returned by an external system during the journey. Which sequence is valid?

  1. Wait node, then condition node, then custom action.
  2. End node, then condition node, then custom action.
  3. Condition node, then custom action, then branch on the response.
  4. Custom action with a response, then a condition node that evaluates the response. Correct answer.

Explanation

The custom action must execute first so its response is available in the journey context, after which a condition node can evaluate that value. Branching before the call would leave the response unavailable.

Question 47Journey Orchestration

A profile is already inside a journey when a new version of that journey is published. What happens to the profile's current path?

  1. The profile is exited from the journey and must re-enter.
  2. The profile restarts the journey from the entry node on the new version.
  3. The profile continues on the version it entered under until it exits. Correct answer.
  4. The profile is immediately moved to the new version at the same node.

Explanation

Profiles already in flight remain on the journey version they entered under and are not migrated mid-path. New admissions after publication follow the new version.

Question 48Journey Orchestration

A developer wants profiles to receive a message at a specific local hour regardless of their time zone. Which combination is required?

  1. A time-of-day condition plus a journey timeout.
  2. An audience-triggered journey with re-entrance enabled.
  3. A wait node scheduled to a specific time combined with the profile time zone setting. Correct answer.
  4. A wait node using a fixed duration plus a send-time optimization setting.

Explanation

Scheduling to a specific time relies on the profile time zone setting so the target hour is interpreted per profile, with a wait node holding the path until that time. Fixed durations and timeouts do not align delivery to a local hour.

Question 49Journey Orchestration

A developer must ensure that a profile who has already received a promotional message in another journey is suppressed in this journey. Which configuration addresses this?

  1. A frequency cap rule applied to the message action Correct answer.
  2. A longer wait node before the action
  3. A condition node that always evaluates to true
  4. A journey timeout shorter than the campaign period

Explanation

Frequency capping rules evaluate prior message history across journeys and suppress sends that exceed the configured limit. Waits, always-true conditions, and timeouts do not consider cross-journey send history.

Question 50Journey Orchestration

Which statement best describes how exit conditions interact with a profile that is currently waiting on a long wait node?

  1. Exit conditions are ignored while a profile is on a wait node.
  2. Exit conditions are evaluated only when the profile reaches the next node after the wait.
  3. Exit conditions can remove the profile during the wait if the criteria become true. Correct answer.
  4. Exit conditions apply only to profiles that have not yet entered the journey.

Explanation

Exit conditions are evaluated while profiles are active in the journey, including during waits, so a qualifying event can remove a profile before the wait completes. They are not deferred until the next node is reached.