When Split For Each is based on information on a page group, the execution order is
-
Deterministic
-
Non-Deterministic
-
None of the above
-
All of the above
When a Split For Each shape processes a page group, the execution order is non-deterministic because the system may iterate through the pages in any order. This is important when the order of processing matters for your business logic. Deterministic execution would require explicit sorting or a different iteration approach. Option C is incorrect because 'non-deterministic' is the correct answer, making it a valid choice.
When a "Split For Each" operation is driven by page-group membership, the execution order across those groups is Non-Deterministic — the tool doesn't guarantee a fixed, repeatable processing order for the split groups, since group membership-based splitting isn't tied to an inherently ordered sequence like an index or sorted key. This reflects a specific behavior of the report/ETL tool referenced (not a general CS principle), so it's taken from the source material's documented behavior rather than something independently verifiable.