Which governance capabilities does SAP Build offer? Note: There are 3 correct answers to this question.

Question

Options

• ALimit the development to predefined templates.
• BEstablish eligibility rules for citizen developers.
• CProvide prebuilt artifacts and use case content packages.
• DIntegrate CI/CD into development processes.
• EImplement guardrails with built-in security.

• A
  11% (3)
• B
  82% (23)
• D
  7% (2)

Explanation

SAP Build's governance framework focuses on controlling who can build, what they can build with, and how securely they build - which maps directly to B, C, and E.

• B (Eligibility rules for citizen developers) is correct because SAP Build includes role-based governance that lets admins define which users qualify as citizen developers and what they're permitted to create.
• C (Prebuilt artifacts and content packages) is correct because SAP Build provides curated, reusable templates and use-case packages - this is a governance mechanism ensuring quality and consistency across low-code projects.
• E (Guardrails with built-in security) is correct because SAP Build enforces security policies at the platform level, preventing citizen developers from inadvertently exposing sensitive data or misconfiguring integrations.

Why the distractors are wrong: A is a mischaracterization - SAP Build doesn't limit development to only templates; it offers templates as a governed starting point while still allowing custom development. D (CI/CD integration) is a DevOps pipeline feature, not a governance capability specific to SAP Build's citizen developer model.

Memory tip: Think of SAP Build governance as "Who, What, and How Safe" - Who can build (B), What they build from (C), and How safely they build (E). CI/CD and template restrictions are red herrings from general software engineering concepts, not SAP Build's governance pillars.

No community discussion yet for this question.