When sizing the robot fleet, the Solution Architect must plan for the worst case: peak data/transaction volume drives how much processing capacity is needed within the SLA window, while the size of the operations (business) team represents the current manual workload/FTE effort the automation is expected to absorb. Together these determine how many robots are required. Option C is wrong because you size for volume peaks, not lows, and shift timings alone do not set capacity. BCP, application performance, and technical approach are relevant design concerns but are not the primary drivers of the robot count.
Community Discussion