5 exercises — master the governance language used in enterprise low-code programmes: Center of Excellence, shadow IT, ALM, app catalogue, and app sprawl.
0 / 13 completed
1 / 13
An enterprise decides to scale low-code adoption across 12 business units. The CTO says: "We need to establish a Center of Excellence before this gets out of hand." What is a CoE in the context of low-code, and what does it do?
The Center of Excellence is the organisational structure that makes enterprise-scale low-code adoption sustainable and governable — understanding CoE vocabulary is essential for anyone involved in low-code strategy discussions.
Core CoE responsibilities:
Responsibility
What it means in practice
Standards & templates
Approved component library, naming conventions, approved connectors list
Training & enablement
Citizen developer training programmes, hackathons, office hours
Dashboard of all flows/apps in tenant, orphaned resource cleanup, dependency management
Risk management
Security review of new connectors, data classification enforcement
The Microsoft CoE Starter Kit:
Microsoft provides a free open-source CoE Starter Kit (a set of Power Apps and Power Automate flows) that a CoE team can deploy to gain visibility over the entire Power Platform tenant — apps, flows, custom connectors, environments, and license consumption — without requiring manual inventory.
Key vocabulary:
• Center of Excellence (CoE) — a cross-functional team governing low-code adoption across an organisation
• DLP policy — Data Loss Prevention policy; controls which connectors can be used together in a flow
• Environment strategy — the plan for how sandbox, development, test, and production environments are structured and access-controlled
• Tenant — in Azure/Power Platform, the entire organisation's instance; all users and environments belong to one tenant
2 / 13
An IT manager discovers that a sales team has built 47 Power Automate flows that send customer data to an unapproved external CRM via a custom connector — all without IT's knowledge. This situation is described as "shadow IT". What is shadow IT and why is it a governance concern?
Shadow IT in the low-code era is particularly complex because the same platform (Power Platform, Salesforce Flow) that IT uses officially is also freely available to all licensed users — creating shadow IT at scale without any technical barriers.
Shadow IT risk taxonomy for low-code:
Risk category
Example in low-code context
Security
Customer PII sent to unapproved external SaaS via unofficial connector
Compliance
GDPR-regulated data leaving the approved data residency region
Operational
Business-critical flow with no documentation, no support SLA, single developer
Integration
Unofficial automation relies on an internal API that IT changes, breaking the flow silently
Key-person dependency
The one person who built the critical flow leaves the company
CoE shadow IT mitigation:
• DLP policy enforcement blocks unapproved connectors from being paired with sensitive data connectors
• Regular CoE inventory scans surface new apps/flows before they become entrenched
• Citizen developer training and official channels give business users approved paths to automate, reducing shadow IT incentive
• "Fusion team" approach: citizen developers work alongside IT in structured projects, eliminating the unofficial parallel track
Key vocabulary:
• Shadow IT — technology used within an organisation without IT department knowledge or approval
• Citizen developer — a business user who builds apps and automations using low-code tools
• Key-person dependency — critical knowledge or skills concentrated in one individual who could leave
• Fusion team — a mixed team of professional developers and citizen developers collaborating on a low-code project
3 / 13
An IT architect presents a governance plan: "We need to implement ALM for all Power Platform solutions — development, test, and production environments with proper solution management." What is ALM in low-code, and why is it more complex than it sounds?
ALM for low-code is consistently underestimated — organisations discover major ALM complexity only after they've already built many solutions in production without environment separation.
Power Platform ALM key concepts:
Concept
What it means
Solution
A container packaging related apps, flows, tables, and connection references into a deployable unit
Environment variable
Configuration value that differs per environment — e.g. API endpoint, SharePoint site URL
Connection reference
A named placeholder for a connector connection; resolves to different actual connections per environment
Managed solution
A solution deployed to test/production that cannot be directly edited — enforces change management
Unmanaged solution
A solution in development that can be freely edited — source of truth is in source control
Typical enterprise environment strategy:
DEV (unmanaged solutions, developer access) → TEST (managed solutions, QA access) → PROD (managed solutions, no developer access)
ALM pipeline automation options:
• Microsoft Power Platform Build Tools for Azure DevOps
• GitHub Actions for Power Platform
• Power Platform CLI (pac) for command-line deployments
Key vocabulary:
• ALM (Application Lifecycle Management) — managing a solution from development through deployment and maintenance
• Solution — a deployable container of Power Platform components
• Environment variable — a per-environment configuration value referenced by a solution
• Connection reference — a portable connector reference that resolves per environment
4 / 13
A CoE team creates a low-code app catalogue and makes it available to all business units. A manager asks: "Why do we need this? Can't people just build what they need?" What is the purpose of a low-code app catalogue?
The low-code app catalogue addresses one of the most common and costly governance failures in large organisations: the same solution being rebuilt independently by multiple teams, wasting resources and fragmenting data.
Why duplicate solutions proliferate without a catalogue:
• Low-code solutions are fast to build — a team can create an expense approval app in a day
• Without visibility, other teams don't know a solution already exists
• Over time, the same business process is automated by 5 different teams with 5 different approaches, none compatible with each other
• Time and money wasted; data is split across incompatible systems; end users get inconsistent experiences
What a mature app catalogue includes:
Catalogue field
Purpose
Solution name & owner
Who built it and who to contact for support
Business function covered
Enables search by business need; prevents duplicates
Support tier (CoE, owner, none)
Sets stakeholder expectations for reliability
Status (active, deprecated, archived)
Prevents adoption of unmaintained solutions
Data sensitivity classification
Informs access control and compliance review requirements
Key vocabulary:
• App catalogue — a central inventory of available low-code solutions with governance metadata
• Solution reuse — adopting or adapting an existing solution rather than building a new one
• Support tier — the level of official support commitment (CoE-managed, owner-managed, community, unsupported)
• App sprawl — uncontrolled proliferation of low-code solutions without governance or lifecycle management
5 / 13
A Power Platform administrator runs a CoE inventory report and finds 340 flows created by employees who have since left the company — they describe the situation as "app sprawl". What is app sprawl and what governance mechanisms prevent it?
App sprawl is an inevitable governance challenge at any organisation that has successfully scaled low-code adoption — it is the "success problem" of low-code governance.
How app sprawl accumulates:
① Citizen developer builds a flow for a specific one-time event (onboarding wave, event registration)
② Flow is never turned off after the event ends
③ Developer changes roles or leaves the organisation
④ Flow has no successor owner — IT receives support tickets for a flow nobody understands
⑤ Connection credentials expire, flow breaks, nobody notices for weeks
⑥ Multiply by hundreds of developers over several years
Governance mechanisms for sprawl prevention:
Mechanism
Description
Maker access control
License-gate production environment; only trained, approved makers can deploy to production
Ownership tracking
CoE inventory links every solution to an active employee; HR system triggers review when owner leaves
Quarterly review
CoE sends usage reports to business owners: "Is this flow still needed?"
Inactivity automation
CoE toolkit monitors flows not run in 90+ days and sends auto-notification to owner
Key vocabulary:
• App sprawl — the uncontrolled accumulation of low-code solutions without governance or lifecycle management
• Orphaned solution — a low-code app or flow whose owner has left the organisation or changed roles
• Maker access control — governance policy restricting who can build and deploy solutions to which environments
• Decommissioning — the formal retirement process for a low-code solution: disable, archive, remove access
6 / 13
David (Lead Developer) comments on a PR: 'This flow is fantastic, but I'm concerned about the lack of versioning. We need to track changes to this connector and ensure we can rollback if necessary.' What does versioning refer to in the context of low-code governance, and why is David's concern valid?
Versioning in low-code governance means managing different states of a solution – typically through numbered releases. This is critical for tracking changes, understanding dependencies, and crucially, enabling rollback to a previous stable version if problems arise. David's concern highlights the importance of control and auditability, which are core elements of responsible low-code development.
7 / 13
David (Lead Developer) comments on a PR: 'This flow is fantastic, but I'm concerned about the lack of versioning. We need to track changes to this connector and ensure we can rollback if necessary.' What does versioning refer to in the context of low-code governance, and why is David's concern valid?
Versioning in low-code governance means managing different states of a solution – typically through numbered releases. This is critical for tracking changes, understanding dependencies, and crucially, enabling rollback to a previous stable version if problems arise. David's concern highlights the importance of control and auditability, which are core elements of responsible low-code development.
8 / 13
David (Lead Developer) comments on a PR: 'This flow is fantastic, but I'm concerned about the lack of versioning. We need to track changes to this connector and ensure we can rollback if necessary.' What does versioning refer to in the context of low-code governance, and why is David's concern valid?
Versioning in low-code governance means managing different states of a solution – typically through numbered releases. This is critical for tracking changes, understanding dependencies, and crucially, enabling rollback to a previous stable version if problems arise. David's concern highlights the importance of control and auditability, which are core elements of responsible low-code development.
9 / 13
Sarah (Business Analyst) sends a Slack message to the Low-Code Governance team: 'I've noticed several teams building completely separate Power Apps for managing customer contacts. It's duplicating effort and creating inconsistencies. What does 'solution standardization' refer to in this context?'
'Solution standardization' focuses on promoting consistency within low-code development. It's about creating reusable components and processes to avoid duplication and ensure that similar tasks are handled in the same way across different applications. Option A is code generation; option C is a prioritization activity, and option D is access control – all unrelated to the core concept.
10 / 13
During a standup meeting, Mark (Developer) says: 'We're using Power Automate to sync data between our legacy database and our new low-code app. We've built a custom connector that handles the transformation. Should we be documenting this transformation logic within the connector itself?'
While documentation is generally good practice, in low-code governance, focusing connectors on their core task (data syncing) is crucial. Transformation logic within a connector can introduce complexity and make it harder to maintain and govern. Option A is overly broad; option C highlights the principle of separation of concerns, and option D proposes an external document that might not be consistently maintained.
11 / 13
A PR description for a new Power Apps solution states: 'This app uses the 'Get Data' connector to pull data from our on-premises SQL Server database. We've configured it with appropriate security settings.' What does 'data source governance' primarily relate to in this scenario?
'Data source governance' centers around controlling access and securing connections to underlying databases. This includes defining who can use which data sources, implementing security measures like user permissions and data masking, and ensuring compliance with data privacy regulations – all vital for maintaining control and reducing risk within a low-code environment.
12 / 13
Emily (PM) asks the Low-Code Governance team: 'We've deployed several citizen developers to build apps using Power Apps. We need a way to ensure that these apps are aligned with our overall business strategy and don't create unnecessary complexity.' What is 'business outcome alignment' in this context?
'Business outcome alignment' is about linking low-code development directly to strategic business goals. This means ensuring that apps built by citizen developers contribute positively to the organization's objectives and don't create isolated, potentially wasteful solutions. Option A describes approval processes; option C focuses on training, and option D is monitoring usage.
13 / 13
During a code review discussion, John (Senior Developer) says: 'I'm seeing a lot of Power Automate flows that don't have clear documentation or traceability. It makes it difficult to understand how they work and what data they're processing.' What is the primary concern raised by John regarding these flows?
John's concern is centered around the critical need for documentation and traceability in low-code development. Without it, governance becomes incredibly challenging – making audits difficult, hindering maintenance efforts, and increasing the risk of errors or security vulnerabilities. Options A, C, and D are specific technical issues that don't represent the core governance problem.
What will I practise in "Low-Code Governance Vocabulary — Low-Code & No-Code Exercises"?
Practice English vocabulary for low-code governance: Center of Excellence, shadow IT, ALM, app catalogue, app sprawl. 5 exercises for IT professionals and citizen developers.
How many exercises are in this module?
This module has 13 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Low-Code & No-Code exercises?
Browse the full Low-Code & No-Code hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.