Ruby on Rails Professional Standards & Competencies 4

Question 1

A Rails API endpoint is returning sensitive user data in error messages in production. What is the immediate professional response?

Accepted Answer

Disable detailed error responses in production via `config.consider_all_requests_local = false` and sanitize error output

Answer

Exposing sensitive data in production error messages is a security incident requiring immediate remediation by disabling detailed errors and sanitizing all error responses.

Question 2

Which competency best describes a Rails developer who writes `before_action :authenticate_user!` only on actions that require authentication?

Accepted Answer

Principle of Least Privilege applied to controller design

Answer

Scoping authentication callbacks to only the actions that require them demonstrates the Principle of Least Privilege, minimizing both attack surface and unintended access restrictions.

Question 3

When should a Rails developer choose background jobs (Sidekiq/GoodJob) over inline processing in a request cycle?

Accepted Answer

For operations that are slow, failure-tolerant, or don't require immediate user feedback (emails, reports, API calls)

Answer

Background jobs are the professional standard for any work that is slow, can fail and be retried, or doesn't need to block the HTTP response.

Question 4

A client asks a Rails developer to implement a feature that would allow bulk-exporting all user PII without authentication. What is the professional response?

Accepted Answer

Refuse to implement it and explain the legal and security risks, proposing a secure authenticated alternative

Answer

Professionals have an ethical obligation to refuse requests that create serious security and legal risks, and to propose safer alternatives rather than simply complying.

Question 5

What does maintaining a well-structured CHANGELOG in a Rails project demonstrate about a developer?

Accepted Answer

Professional communication skills and commitment to transparent version history for team members and users

Answer

A maintained CHANGELOG demonstrates professionalism by giving team members and users a clear, human-readable history of changes, decisions, and breaking changes over time.

Ruby on Rails Practice Test

Ruby on Rails Practice Test

Ruby on Rails Professional Standards & Competencies 4