Why deployment preparation matters in Ruby on Rails - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is asset precompilation important before deploying a Rails app?

In Rails, what is the main reason to precompile assets before deployment?

A To generate user authentication tokens for security.

B To automatically update the database schema during deployment.

C To clear all cached data from the server before starting.

D To speed up page loading by serving compressed and combined CSS and JavaScript files.

💡 Hint

Think about how browsers load styles and scripts efficiently.

Precompiling assets combines and compresses CSS and JavaScript files. This reduces the number of requests and file sizes, making pages load faster for users.

❓ component_behavior

intermediate

What happens if database migrations are skipped during deployment?

Consider a Rails app deployment where database migrations are not run. What is the likely outcome when the app starts?

A The app will run normally but with slower performance.

B The app will automatically create missing tables without migrations.

C The app may crash or show errors due to missing or outdated database tables or columns.

D The app will ignore database calls and serve static pages only.

💡 Hint

Think about how Rails uses migrations to keep the database structure in sync with the code.

Skipping migrations means the database schema may not match the app's expectations. This causes errors when the app tries to access missing tables or columns.

🔧 Debug

advanced

Identify the deployment issue from this Rails log snippet

During deployment, the Rails app logs show: ActionController::RoutingError (No route matches [GET] "/assets/application.js"). What is the most likely cause?

A The database migrations were not run, causing routing errors.

B Assets were not precompiled before deployment, so the server can't find the JavaScript file.

C The server is missing the Ruby interpreter.

D The app's secret key base is not set, causing asset loading to fail.

💡 Hint

Focus on the missing asset file in the error message.

The error shows the app can't find the JavaScript asset. This usually happens if assets were not precompiled, so the files don't exist in the public folder.

❓ state_output

advanced

What is the state of the Rails app after a failed migration during deployment?

If a migration fails halfway during deployment, what is the likely state of the database and app?

A The database schema is partially updated, causing inconsistent app behavior or errors.

B The database automatically rolls back to the previous stable state.

C The app ignores the failed migration and continues running normally.

D The app switches to a maintenance mode automatically.

💡 Hint

Consider what happens if a migration script stops in the middle.

Failed migrations can leave the database in a half-changed state, which can cause errors or unexpected behavior until fixed.

📝 Syntax

expert

Which config setting correctly enables Rails production logging to STDOUT?

In config/environments/production.rb, which line correctly configures Rails to log to standard output for deployment environments like Heroku?

A config.logger = ActiveSupport::Logger.new(STDOUT)

B config.log_to_stdout = true

C config.logger = Logger.new(STDOUT)

D config.log_level = :stdout

💡 Hint

Look for the correct class used by Rails for logging.

Rails uses ActiveSupport::Logger to handle logging. Setting config.logger = ActiveSupport::Logger.new(STDOUT) sends logs to standard output.