System architecture choices: Which of the following is NOT typically an advantage of decentralized processing when compared to centralized processing?

Introduction / Context:
Computing can be centralized (resources in one place) or decentralized (resources distributed to departments or sites). Each approach has trade-offs across cost, control, responsiveness, and reliability. Understanding these helps architects match technology to organizational needs.

Given Data / Assumptions:

• Decentralization places processing closer to users.
• Local autonomy may boost responsiveness and productivity.
• Central IT’s direct control typically decreases in decentralized models.

Concept / Approach:
Decentralized processing often reduces wide-area communication needs (local processing), improves perceived reliability via fault isolation, and increases user responsiveness—potentially boosting productivity. However, it generally reduces centralized control, making standardization, governance, and uniform security harder. Therefore, “increased computer system control” is not an advantage of decentralization.

Step-by-Step Solution:

Verification / Alternative check:
IT governance literature notes centralization increases standardization and control; decentralization increases flexibility at the expense of uniform control.

Why Other Options Are Wrong:
They are plausible benefits of decentralization in many contexts.

Common Pitfalls:
Ignoring hybrid models (federated IT) that attempt to balance control with local agility; assuming “reliability” always increases—design matters.

Final Answer:
increased computer system control