Why does SAP recommend IT governance for citizen development?

Question

Options

• ATo ensure applications are secure, scalable, and compliant with corporate standards.
• BTo centralize control and decision making within low-code development.
• CTo exercise financial control over all software development projects.

• A
  91% (21)
• B
  4% (1)
• C
  4% (1)

Explanation

SAP recommends IT governance for citizen development primarily to ensure that applications built by non-professional developers (citizens) remain secure, scalable, and aligned with corporate standards - without IT governance, citizen-built apps can introduce security vulnerabilities, data compliance violations, or technical debt that burdens the broader organization.

Why the distractors are wrong:

• B is wrong because IT governance in citizen development is not about centralizing control and decision-making - the whole point of citizen development is to decentralize development; governance provides guardrails, not a bottleneck.
• C is wrong because financial control is a secondary concern at best; governance here is about quality, risk, and compliance, not budget oversight of projects.

Memory tip: Think of IT governance as a "safety net," not a "control tower" - it exists to catch problems (security, scale, compliance) while still letting citizens build freely. The keyword trio secure + scalable + compliant maps directly to the three pillars SAP emphasizes for safe citizen development.

No community discussion yet for this question.