The correct answer is B. Ability to toggle between multiple records. The uploaded UX Designer study guide explicitly identifies this requirement as a reason to recommend Console navigation. Console navigation is designed for users who work intensively with multiple records and related information during the same session. Rather than continually leaving one record page and opening another, users can maintain several records within the console workspace and switch between them efficiently. This makes the console particularly valuable for sales or service roles where users frequently compare, reference, or update multiple related records.
Option A is not the defining requirement in the study-guide scenario. Although console applications can support efficient multi-record workflows, the requirement specifically associated with the answer is the ability to toggle between multiple records.
Option C points in the opposite direction. Users whose work occurs primarily in the field generally have stronger mobile and simplified-navigation requirements rather than a desktop-oriented multi-record console workspace.
From a UX perspective, the navigation model should correspond to the user's task pattern. Standard navigation suits more linear interaction, whereas Console navigation is better suited to high-volume, multi-record work where reducing navigation overhead improves productivity.
Study Guide reference/topics: Console Navigation, Standard Navigation, multi-record workflows, productivity, Declarative Design.
==================================
