050-SEPROGRC-01 · Question #12
When would a solution demonstration be performed, rather than a Proof-of-Concept (POC) be built? (Choose two)
The correct answer is A. A potential customer needs an initial introduction to RSA Archer. D. A current customer is considering adding a new solution to their license and wants to see how the. A solution demonstration is appropriate for introductory or evaluative scenarios where a customer needs to see capabilities without hands-on piloting. A POC is used when a customer is ready to test a real business process in the actual environment.
Question
When would a solution demonstration be performed, rather than a Proof-of-Concept (POC) be built? (Choose two)
Options
- AA potential customer needs an initial introduction to RSA Archer.
- BA current customer wants to customize an existing solution but isn't sure where to begin.
- CA potential customer wants to see how a business process could be incorporated into RSA
- DA current customer is considering adding a new solution to their license and wants to see how the
- EA current customer is ready to pilot a representative business process and needs access to RSA
How the community answered
(50 responses)- A74% (37)
- B4% (2)
- C14% (7)
- E8% (4)
Why each option
A solution demonstration is appropriate for introductory or evaluative scenarios where a customer needs to see capabilities without hands-on piloting. A POC is used when a customer is ready to test a real business process in the actual environment.
A potential customer needing an initial introduction benefits from a demonstration because they are at the awareness stage and not yet ready for a hands-on POC.
A current customer wanting to customize an existing solution requires hands-on work and guidance, making it more suited to a POC or consulting engagement.
Incorporating a specific business process into the platform implies a level of hands-on configuration that aligns with a POC rather than a passive demonstration.
A current customer evaluating whether to add a new solution to their license wants to see its capabilities, which is best served by a demonstration rather than a full POC build.
Piloting a representative business process with system access is the definition of a POC, not a solution demonstration.
Concept tested: RSA Archer pre-sales demonstration vs. POC scenarios
Topics
Community Discussion
6The correct answers are A and D. A solution demonstration is the right move when you are showing off existing, out-of-the-box RSA Archer capability, either to introduce the product to someone who has never seen it or to let a current customer preview a solution they might add to their license. Both of those scenarios call for a polished, pre-built walkthrough because the goal is to show what already exists, not to prove that something custom can be built. A POC, by contrast, gets built when you need to actually construct something to answer the question, like piloting a real business process or exploring how a customization might work. The moment you are building or configuring to prove a point rather than demonstrating a finished thing, you have crossed into POC territory, which is why C and E are wrong here and why B is wrong too.
I got A and D on this one, but I want to make sure I understand the reasoning and not just memorize it. The way I read it, a demo is basically "here, let me show you what already exists," and a POC is more like "let us build something to prove this could work for your specific situation," so A fits because a potential customer getting their first look just needs to see the product, and D fits because a current customer evaluating a new add-on solution still just needs to see what it does before committing. Can someone clarify what specifically pushes C into POC territory instead of demo, since that one also involves a potential customer, just like A?
I initially flagged C as a demo scenario because it mentions showing a business process, but the word "incorporated" is the tell, that language signals customization work, which is POC territory, not a canned walkthrough. A and D are both pre-sales or expansion situations where you are showing existing, pre-built functionality to someone who has not yet committed, which is the textbook trigger for a solution demonstration rather than a build.
The wording on D cuts off but you can figure it out, it is pointing to a current customer scoping a new solution add-on, which is exactly the demo scenario because nothing has been committed yet and you are still in the evaluation stage. A trips people up because they overthink it, a cold intro to Archer for a prospect is a demo by definition, not a POC, since a POC requires an actual business process to pilot against and a prospect at that stage does not have one scoped out yet.
So "demo" means showing existing product, not building anything new, right?
Mostly yes, though in some lab or POC contexts you might hear "demo" used loosely to mean a quick build-and-show, so worth checking what the specific question stem implies before locking that in.