APIGEE-API-ENGINEER practice question 18 of 25

You are working with the product owners and uncover an opportunity for new functionality. The product owners ask you to quickly outline the desired functionality. Which approach should you use?

Full set: 126 questions
Answer options
A: Use a business requirements document.
B: Use a behavior driven development "given-when-then" script to outline the main steps Correct answer
C: Implement a proof of concept
D: Implement a suite of unit test cases that qualify a working API
Correct Answer:
B. Use a behavior driven development "given-when-then" script to outline the main steps
Explanation

Behavior-Driven Development (BDD) uses the "Given-When-Then" Gherkin syntax to describe system behavior in a natural, human-readable language. This approach is ideal for quickly outlining functionality because it creates a common, unambiguous language for both technical teams and non-technical stakeholders like product owners. It focuses on concrete examples of user interactions and expected outcomes, facilitating clear communication and a shared understanding of the requirements. This directly addresses the need to "quickly outline the desired functionality" in a collaborative setting without the overhead of formal documentation or premature implementation.

Why Incorrect

A: A business requirements document is a formal, detailed, and time-consuming document, which contradicts the need to "quickly outline" functionality. C: Implementing a proof of concept is a development task to prove technical feasibility, not a method for quickly outlining functional requirements with product owners. D: A suite of unit tests is a technical artifact written in code for developers and is not an effective communication tool for outlining functionality to product owners. ---

References

1. Google Cloud Architecture Center

DevOps capabilities: Technical practices

"Test-driven development": This document

while focused on TDD

explicitly describes BDD as a related practice. It states

"Behavior-driven development (BDD) is an extension of TDD that uses a natural-language

domain-specific syntax to describe the behavior of a system." This supports using a natural-language syntax for defining functionality

which is ideal for collaboration with product owners.

2. Apigee Documentation

"The API-first approach to design": The API-first approach

central to Apigee's philosophy

emphasizes creating a clear API contract before any code is written. The documentation states

"With an API-first approach

applications are designed around an API contract... This allows teams to work in parallel." BDD scripts serve as an excellent

human-readable form of this API contract

outlining the behavior before implementation.

3. Pautasso

C.

& Wilde

E. (2014). RESTful API Design with Behavior-Driven Development. In Proceedings of the 5th International Workshop on RESTful Design (WS-REST 2014). This peer-reviewed academic paper discusses how BDD is a suitable methodology for API design. It highlights that BDD scenarios "can be used as a communication tool between the different stakeholders (customers

developers

testers) to define and agree on the API design." (Section 3

Paragraph 1). DOI: https://doi.org/10.1145/2597278.2597281

Scroll to Top