CSE Customer Needs Analysis & Solution Design 4 β Questions and Answers
Question 1: What is the primary purpose of a 'solution sandbox' or proof-of-concept (PoC) in the sales engineering process?
- To demonstrate the full product feature set
- To validate that the proposed solution addresses the customer's specific requirements in their environment (Correct answer)
- To provide a discounted trial version to close the deal faster
- To allow the customer's developers to customize the product
Correct answer: To validate that the proposed solution addresses the customer's specific requirements in their environment
A PoC is scoped to the customer's key requirements and validates feasibility before full commitment, reducing risk for both parties.
Question 2: Which of the following is an example of a non-functional requirement in solution design?
- The system must allow users to export reports as PDF
- The system must process 10,000 transactions per second with 99.99% uptime (Correct answer)
- The system must integrate with Salesforce CRM
- The system must support two-factor authentication login
Correct answer: The system must process 10,000 transactions per second with 99.99% uptime
Non-functional requirements define system performance, reliability, and scalability constraints rather than specific behaviors or features.
Question 3: When conducting a 'current state' versus 'future state' analysis, what is the sales engineer trying to establish?
- The customer's current vendor contract expiration date
- The gap between where the customer is today and where they need to be, which the solution will bridge (Correct answer)
- The customer's technology roadmap for the next five years
- A comparison of your product's features versus the customer's legacy system
Correct answer: The gap between where the customer is today and where they need to be, which the solution will bridge
The current-to-future state gap defines the problem space and directly informs what the solution must accomplish.
Question 4: A customer's stated requirement conflicts with their underlying business goal. What should the sales engineer prioritize?
- The stated requirement, because the customer is always right
- The underlying business goal, after transparently explaining the conflict to the customer (Correct answer)
- Whichever option is faster and cheaper to implement
- The requirement that is easiest for your product to fulfill
Correct answer: The underlying business goal, after transparently explaining the conflict to the customer
Satisfying the underlying business goal delivers real value; a solution that meets a stated requirement but misses the goal will lead to customer dissatisfaction.
Question 5: What is the main risk of conducting needs analysis only with a customer's IT department?
- IT teams tend to over-engineer requirements
- You may miss the business, operational, and financial requirements held by other stakeholders (Correct answer)
- IT requirements are too technical to map to your solution
- IT budgets are rarely sufficient to fund the full solution
Correct answer: You may miss the business, operational, and financial requirements held by other stakeholders
IT stakeholders focus on technical fit but may not represent the full set of business, compliance, or financial requirements critical to solution success.
Question 6: Which of the following best describes 'consultative solution design'?
- Presenting a pre-built product package and letting the customer choose modules
- Co-creating a solution with the customer based on a deep understanding of their unique needs and context (Correct answer)
- Offering the cheapest configuration to win the deal quickly
- Designing the solution independently and presenting it as a completed plan
Correct answer: Co-creating a solution with the customer based on a deep understanding of their unique needs and context
Consultative design treats the customer as a partner, resulting in solutions that are better adopted and more defensible against competitors.
Question 7: When a solution requires integrating with a customer's legacy system, what should the sales engineer do during needs analysis?
- Assume standard API connectivity will suffice
- Document the legacy system's data formats, connectivity options, and constraints before committing to integration scope (Correct answer)
- Recommend the customer replace the legacy system as part of the deal
- Defer integration questions to the implementation team post-sale
Correct answer: Document the legacy system's data formats, connectivity options, and constraints before committing to integration scope
Legacy system constraints can dramatically affect integration complexity and cost; undiscovered constraints post-sale cause scope creep and customer dissatisfaction.
What is the primary purpose of a 'solution sandbox' or proof-of-concept (PoC) in the sales engineering process?