What are potential disadvantages of shadow IT in low-code development projects? Note: There are 2 correct answers to this question.

Question

Options

• ACompliance issues
• BFaster implementation
• CHigher autonomy of low-code developers
• DSecurity risks

• A
  90% (44)
• B
  2% (1)
• C
  8% (4)

Explanation

Shadow IT refers to technology solutions built or used outside official IT oversight - a common risk in low-code platforms where business users can rapidly create their own apps.

A (Compliance issues) and D (Security risks) are correct because shadow IT bypasses the formal governance processes that ensure data handling meets regulatory requirements (e.g., GDPR, HIPAA) and that applications are secured against vulnerabilities. Without IT oversight, sensitive data may be stored insecurely, access controls may be weak, and audit trails may be absent.

B (Faster implementation) is wrong because it's actually a benefit of shadow IT, not a disadvantage - the whole appeal is that business users can build solutions quickly without waiting on IT departments.

C (Higher autonomy of low-code developers) is also wrong for the same reason - increased autonomy is a feature, not a drawback, from the developer's perspective.

Memory tip: Think of shadow IT as "working in the dark" - the speed and freedom are attractive (B and C), but operating outside oversight inevitably creates legal exposure (compliance) and attack surface (security). The two disadvantages are the two risks that governance exists to prevent.

No community discussion yet for this question.