1Z0-1041-20 · Question #24
Which is not a step that can be followed to create a Story?
The correct answer is C. Share the Story in presentation mode by setting the reportMode parameter in the project properties to. Explanation/Reference:
Question
Which is not a step that can be followed to create a Story?
Options
- ACreate and position annotations on the canvas as desired.
- BCapture a story insight from one or more Visualization canvases in a project by navigating from
- CShare the Story in presentation mode by setting the reportMode parameter in the project properties to
How the community answered
(39 responses)- A13% (5)
- B5% (2)
- C82% (32)
Explanation
Explanation/Reference:
Topics
Community Discussion
9
Petros O.Jun 27, 2026C is the odd one out. Setting reportMode in project properties is how you share or present a Story, not how you create one, and conflating the two is exactly the kind of trap Oracle loves to put in these exams. Creating a Story involves working on the canvas, capturing insights from visualizations, and arranging annotations, none of which has anything to do with flipping a presentation flag in properties.
Lena V.Jun 29, 2026Petros nails the core trap, but worth adding that the canvas work itself, capturing and arranging, is only half the story because you also need at least one visualization pinned before Oracle considers the Story saveable.
Fatima Z.Jun 27, 2026Oh C is the trap door on this one, because "Share in presentation mode" sounds like part of the workflow, but sharing is what you do AFTER you build the story, not a creation step. Remember it with this: A-B-C where only A and B actually Build the Canvas Content. The moment you see "set the reportMode parameter in project properties," that is your DELIVERY phase, not your BUILD phase, so C is the odd one out and your correct pick here.
Lena V.Jun 27, 2026Solid breakdown, and worth adding that "presentation mode" is itself a flag word on the exam, because you cannot present what you have not yet built, so if any option mentions presenting or sharing before the canvas steps are done, it is always the distractor.
Lena V.Jun 27, 2026C is right, reportMode is a red herring. What part of the Story workflow trips you up most?
Luis F.Jun 29, 2026Yeah reportMode is mostly noise until you get to the very end of the workflow, but honestly the trickiest part for me was wrapping my head around how Story points get inherited vs. overridden at the sub-task level.
Luis F.Jun 27, 2026Got this one wrong the first time I practiced it, so let me save you the headache. The answer is C because setting the reportMode parameter in project properties is how you share or present a Story after it already exists, not how you build one in the first place. Creating a Story actually involves things like positioning annotations on your canvas (A) and capturing insights from your visualization canvases (B), those are legitimate authoring steps inside Oracle Analytics. On my actual exam I almost picked B because I second-guessed myself thinking "capture" sounded weird, but then I remembered that reportMode is purely a delivery/sharing config and has nothing to do with the creation workflow, so I switched to C and it was right.
Wesley A.Jun 27, 2026Going with A on this one and I feel pretty solid about it. Creating and positioning annotations is something you do on a canvas when you are building out your visualizations, not a defined step in the Story creation workflow itself. The Story process is specifically about capturing insights from those canvases and then presenting them, which is exactly what B and C describe. I got burned on a similar question my first time through because I was mixing up canvas-level actions with Story-level actions, and that confusion is exactly what this question is testing. Annotations live in the visualization layer, not the Story layer, so A does not belong in that sequence.
Luis F.Jun 28, 2026Hey Wesley, actually the correct answer is C on this one. The Story creation workflow does include a specific step for adding annotations because that is how you attach context and narrative directly to the insights you are capturing, so it is very much part of the Story layer and not just a canvas-level action.