Explanation
The three statements that should be considered before using Goals in Journey Builder are:
* Goals are created to evaluate journey performance. This statement is true, as goals are used to measure how well a journey is achieving its desired outcome or objective. Goals can also help NTO to optimize their journey by identifying which activities or paths are more effective in reaching the goal1.
* Goals can act as exit criteria. This statement is true, as goals can be configured to exit contacts from a journey when they meet the goal criteria. This can help NTO to save resources and avoid sending irrelevant messages to contacts who have already achieved the desired outcome or objective1.
* Contacts are evaluated against the goal after a wait activity. This statement is true, as contacts are only evaluated against the goal when they reach a wait activity in the journey. Wait activities are used to pause the journey for a specified amount of time or until a specific date or event occurs. After the wait period ends, contacts are evaluated against the goal and either exit the journey or continue to the next activity

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
Before updating and increasing their session timeout setting, the admin should review the following three considerations:
* Frustration of users upon timeouts. The admin should consider how users feel when their sessions expire and they have to log in again. Increasing the session timeout setting can reduce user frustration and improve user experience by allowing them to stay logged in longer.
* Security risk of unauthorized users for longer timeout settings. The admin should consider how longer timeout settings can increase the security risk of unauthorized users accessing Marketing Cloud.
Increasing the session timeout setting can expose user accounts and data to potential threats if users leave their devices unattended or share them with others.
* Change impacts all users. The admin should consider how changing the session timeout setting will affect all users within their account or business unit. Increasing the session timeout setting will apply to all users who log in to Marketing Cloud after the change, regardless of their roles or permissions. The other option is incorrect because:
* Typical length of time users spend in Marketing Cloud. This is not a consideration for updating and increasing their session timeout setting, as it does not affect the security or user experience of Marketing Cloud. The typical length of time users spend in Marketing Cloud may vary depending on their tasks and needs, but it does not determine how long their sessions should last before expiring.