Spring Framework Communication & Stakeholder Relations 5 — Questions and Answers
Question 1: A Spring team's on-call rotation lacks documentation. A new team member is on call for the first time. Which gap is most critical to address before their shift?
- Sharing the team's coffee preferences
- Providing an escalation contact list, service runbooks, and alert context documentation (Correct answer)
- Giving them access to production only
- Assigning a buddy without any written resources
Correct answer: Providing an escalation contact list, service runbooks, and alert context documentation
Escalation contacts, runbooks, and alert context are the minimum documentation needed for an on-call shift to be manageable.
Question 2: In Spring-based agile development, which ceremony is primarily designed to manage stakeholder expectations and demonstrate progress?
- Daily stand-up
- Sprint review / demo (Correct answer)
- Backlog grooming
- Team retrospective
Correct answer: Sprint review / demo
Sprint reviews are the dedicated ceremony for demonstrating working software to stakeholders and gathering their feedback.
Question 3: A Spring service's SLA is defined as 99.9% uptime. How should the team communicate a month where uptime was 99.7%?
- Round up to 99.9% in the report
- Report the actual 99.7%, explain the root cause, and describe corrective actions taken (Correct answer)
- Do not publish an SLA report for that month
- Redefine the SLA to 99.7% retroactively
Correct answer: Report the actual 99.7%, explain the root cause, and describe corrective actions taken
Honest SLA reporting with root cause and corrective actions maintains stakeholder trust even when targets are missed.
Question 4: A Spring integration test suite takes 45 minutes and is blocking the CI pipeline. How should this be communicated to the team to drive change?
- Accept the slow pipeline and say nothing
- Present the data on pipeline bottleneck impact, lost developer productivity, and propose parallelization options (Correct answer)
- Just skip the slow tests silently
- Blame the QA team for writing too many tests
Correct answer: Present the data on pipeline bottleneck impact, lost developer productivity, and propose parallelization options
Data-driven communication on productivity impact frames the issue as a business problem and motivates prioritizing the fix.
Question 5: When onboarding a new engineer to a Spring microservices codebase, which communication artifact provides the most durable value?
- A one-time verbal walkthrough
- An up-to-date architecture diagram, service inventory, and local setup guide in the repository (Correct answer)
- A 10-hour recorded meeting from two years ago
- Telling them to read all the Jira tickets
Correct answer: An up-to-date architecture diagram, service inventory, and local setup guide in the repository
Living documentation in the repository—architecture diagrams, service inventory, and setup guides—is self-service and stays close to the code it describes.
Question 6: A Spring team receives conflicting priority signals from two stakeholders. What is the correct escalation path?
- Pick the stakeholder the team likes better
- Document the conflict, present it to both stakeholders, and escalate to a common decision-maker if unresolved (Correct answer)
- Ignore both stakeholders and work on technical debt
- Implement both priorities simultaneously without informing anyone
Correct answer: Document the conflict, present it to both stakeholders, and escalate to a common decision-maker if unresolved
Documenting and surfacing the conflict to a common decision-maker creates a transparent resolution without the team making an arbitrary call.
Question 7: Which Spring Boot feature can be leveraged to communicate build and version information automatically to operations teams via an API endpoint?
- Spring Data JPA
- Spring Boot Actuator /actuator/info with build-info.properties (Correct answer)
- Spring Security OAuth2
- Spring Batch job launcher
Correct answer: Spring Boot Actuator /actuator/info with build-info.properties
The /actuator/info endpoint exposes build metadata such as version, git commit, and build time when build-info.properties is generated at build time.
A Spring team's on-call rotation lacks documentation.
A new team member is on call for the first time.
Which gap is most critical to address before their shift?