DA0-001 · Question #12
A publishing group has requested a dashboard to track submissions before publication. A key requirement is that all changes are tracked, as multiple users will be checking out documents and editing…
The correct answer is A. Display the version number next to each submission on the dashboard. The core requirement is tracking changes across multiple users and edits. Displaying the version number next to each submission directly addresses this by giving users a clear, visible indicator of which iteration of a document they are viewing or editing. A data refresh date…
Question
A publishing group has requested a dashboard to track submissions before publication. A key requirement is that all changes are tracked, as multiple users will be checking out documents and editing them before submissions are considered final. Which of the following is the BEST way to meet this stakeholder requirement?
Options
- ADisplay the version number next to each submission on the dashboard.
- BPresent a data refresh date at the top of the dashboard.
- CConfirm the dashboard is adhering to the corporate style guide.
- DUse permissions to ensure users only see certain versions of the submissions.
How the community answered
(26 responses)- A85% (22)
- B4% (1)
- C8% (2)
- D4% (1)
Explanation
The core requirement is tracking changes across multiple users and edits. Displaying the version number next to each submission directly addresses this by giving users a clear, visible indicator of which iteration of a document they are viewing or editing. A data refresh date (B) only shows when data was last updated, not which version a document is on. Adhering to a style guide (C) is a design concern, not a version-tracking solution. Restricting permissions (D) controls access but does not fulfill the tracking requirement - it may actually hinder collaboration.
Topics
Community Discussion
No community discussion yet for this question.