C_SIGPM sample questions & answers

Velmora Textiles, a mid-sized fabric maker in Porto, Portugal, grew from one weaving line to five in just three years. Order fulfillment now slips constantly. When a wholesale order arrives by email, a sales clerk keys it into a spreadsheet, then verbally tells the planning desk, who scribble it onto a whiteboard for the dye house. Nobody has ever agreed where one team's job ends and the next begins, so dye batches are sometimes started before credit is checked and sometimes wait days because each team assumes another owns the next step. Two large orders were dyed the wrong colour last month because the shade code lived only in the clerk's head. The five lines now share suppliers and machines, so a stall in one team's step quietly cascades into the others, and the wholesale accounts that drive most revenue are hit hardest. Leadership blames "careless staff," yet every team is faithfully following what it believes is the process; the trouble appears at the seams between them. A new operations lead wants to address the root cause rather than bolt on more checking that would only slow every order further.

Which recommendation best addresses the underlying cause of Velmora's fulfillment failures?

At Halcyra Papermill in Gothenburg, the process office has published dozens of diagrams describing pulp handling and shipping. Reviewers notice that the same warehouse management system appears under three different names across the diagrams: one team wrote it one way, another abbreviated it, and a third used an old project label. When the system was recently renamed, an analyst had to open every affected diagram by hand to update the label, and several were missed, leaving stale names in production models. The underlying cause is that each modeler typed the system name as free text directly onto activities and data objects rather than referencing a shared, governed entity. Without a single source for such recurring objects, terminology drifts, searches miss diagrams, and any future change means another manual sweep. Leadership wants a way to keep names consistent and to make a single edit propagate everywhere the system is used. As the Signavio consultant advising the modeling team, you must recommend a sustainable approach that fixes the root cause rather than patching the current symptoms one diagram at a time.

What should you recommend to keep recurring object names consistent across all diagrams?

Havstein Tannery in Trondheim, Norway modeled its raw-hide intake process in SAP Signavio Process Manager. After an 'Inspect incoming hide' task, an analyst placed a parallel gateway that splits flow into two branches, 'Route to tanning line' and 'Return batch to supplier', and both branches then continue as if they always execute together. In practice each delivered hide is either accepted and sent to tanning or rejected and returned, never both. Reviewers notice that when the model is walked through, every inspected hide appears to travel down both branches at once, producing token counts that never reconcile at the downstream merge. The quality lead asks how the diagram should represent this accept-or-reject decision so that exactly one branch runs for each hide, driven by the inspection result. The team wants the correction to reflect standard BPMN 2.0 flow-control semantics rather than a workaround such as deleting one branch or adding manual notes. They also want the fragment to remain readable to auditors who follow the flow. Which change correctly captures the intended behaviour?

Which change correctly models the accept-or-reject decision after inspection?