Ruby on Rails Communication & Stakeholder Relations 4

Question 1

A Rails project is behind schedule. When should stakeholders be informed?

Accepted Answer

As soon as the delay is identified, with an updated timeline and mitigation plan

Answer

Early disclosure of delays with a recovery plan demonstrates responsibility and gives stakeholders time to adjust their own plans.

Question 2

Which Rails feature can be used to expose a read-only status page for external stakeholders monitoring system health?

Accepted Answer

A dedicated /status or /health endpoint returning JSON metrics

Answer

A /health or /status endpoint provides a lightweight, safe way for stakeholders and monitoring tools to check application status.

Question 3

A stakeholder requests that a sensitive user data field be added to Rails API responses. What should the developer communicate?

Accepted Answer

Raise data privacy and compliance concerns and propose alternative minimal-disclosure approaches

Answer

Proactively flagging privacy and compliance implications ensures stakeholders understand the risk before making a final decision.

Question 4

When a Rails deployment causes unexpected downtime, which post-incident communication artifact is most valuable?

Accepted Answer

A blameless post-mortem document with timeline, root cause, and preventive actions

Answer

A blameless post-mortem promotes psychological safety while systematically improving processes to prevent recurrence.

Question 5

A stakeholder wants daily updates on Rails feature progress. What sustainable communication approach balances their need with team focus?

Accepted Answer

Use a project board (e.g., GitHub Projects or Jira) with real-time status they can self-serve

Answer

Self-service project boards give stakeholders visibility on demand without interrupting developer flow.

Ruby on Rails Practice Test