Ruby on Rails Web Development Basics

The correct Rails command is 'rake db:migrate' - this applies pending migrations to the database. Options A and C use incorrect verb forms ('migrations' and 'migrates' instead of 'migrate'), and D incorrectly adds 'project' as an argument. The Rails migration syntax follows the pattern 'rake db:taskname'.

WEBrick (Web Engine from Ruby) is the built-in web server that ships with Rails. It's included in Ruby's standard library and used by default when you run 'rails server' in development. Options A, B, and D are fictitious names meant to sound similar but don't exist.

In Rails, every model class inherits from ActiveRecord::Base (or ApplicationRecord in Rails 5+, which itself inherits from ActiveRecord::Base). This provides ORM functionality, database interaction, validations, and associations. ActiveRecord is the core Rails component that connects models to database tables. ActiveModel is for non-database models, and the other options don't exist.

Rails follows the Model-View-Controller (MVC) architectural pattern, which separates application logic into three interconnected components. The Model handles data and business logic, the View manages the user interface, and the Controller processes user input and coordinates between Model and View.

CRUD represents the four basic operations of persistent storage: Create (insert new records), Read (retrieve existing data), Update (modify existing records), and Delete (remove records). This pattern is fundamental in database management and web application development.

Ruby is an interpreted language, meaning code is executed directly without prior compilation, and it's purely object-oriented where everything (including numbers and booleans) is an object. This combination allows for dynamic typing and flexible programming styles.

In Rails (especially older versions with script/generate), scaffolding syntax uses field:type pairs separated by spaces. Option D correctly shows name:string type:string, which specifies two fields with their data types. The other options use incorrect syntax like arrows, equals signs, or malformed type declarations.

In the MVC architecture, the Controller is responsible for handling incoming HTTP requests from web browsers. It processes the request, interacts with the Model for data operations, and selects the appropriate View for rendering the response. The Model and View don't directly handle browser requests.

To create a new Rails application, you simply type rails followed by your application name. The Rails framework automatically generates all necessary directories and files. Options A, C, and D incorrectly add create or app keywords that aren't part of the standard command syntax.

Rails uses YAML format for configuration files, and database settings are stored in config/database.yml. This file contains connection details for different environments (development, test, production). The .yml extension is standard for YAML files, not .xml or .rb.

ActionPack is the Rails framework component that handles routing, controllers, and view rendering. It manages web requests by mapping URLs to controller actions and coordinating between models and views. This is part of Rails' modular architecture, which also includes ActiveRecord for databases and ActionView for presentations.

ActionMailer is a Rails framework component for sending email, not a JavaScript library. It provides a simple way to create and send emails using Ruby-like templates. JavaScript libraries for browser functionality are completely separate from server-side email functionality in Rails.

To import an image into a page in Dialogue, you use the menu sequence Insert -> Drawing Object -> Image. The Insert menu is the starting point for adding various elements, Drawing Object is the category, and Image is the specific object type. The other options incorrectly start with Image or use the wrong menu paths.