Free HTML5 Application Development Practice Questions

The correct selections are C and D because both declare a function as a property of an object, which is the defining characteristic of a JavaScript method. MDN describes a method as a function associated with an object, or more specifically, an object property whose value is a function. In option C, Score: function() { ... } is object-literal syntax. It defines a property named Score whose value is an executable function, so that property behaves as a method of the object. In option D, this.Score = function() { ... } assigns a function to the Score property of the current object instance. MDN notes that this is commonly used inside object methods to refer to the object the method is attached to. Option B does not declare a method; it calls Score() and assigns the return value. Option A is only an incomplete or ordinary variable declaration and does not create a function-valued object property. References/topics: JavaScript objects, custom classes, methods, function expressions, this.

The correct 2D transformation functions are matrix() and skew(). CSS transformations are applied through the transform property, which accepts transform functions that can move, rotate, scale, skew, or otherwise alter an element visually in two-dimensional or three-dimensional space. MDN describes the < transform-function > type as representing transformations that affect an element’s appearance and can operate in 2D or 3D space. The matrix() function is valid because it defines a homogeneous two-dimensional transformation matrix, allowing multiple transform effects to be represented in a single function. The skew() function is also valid because it distorts an element along the 2D plane. move() is not a CSS transform function; the standard movement function is translate(). scroll() is not a transform function; scrolling is controlled through overflow and scroll APIs. zoom() is not a CSS3 2D transform function. References/topics: CSS3 transforms, transform property, 2D transformation functions, matrix(), skew().

==========

First drop-down: flex boxes

Second drop-down: background-size

Third drop-down: cover

The layout changes from a stacked mobile layout to a multi-column desktop layout without relying on media queries. That behavior is commonly achieved with responsive flex boxes, where items can wrap naturally based on the available width. The header image must fill the available header area on both mobile and desktop. For that requirement, the correct CSS property is background-size, and the correct value is cover. background-size: cover scales the image so the entire header area is filled, even if part of the image is cropped. contain would preserve the full image but could leave empty space, and auto would keep the image at its natural size.

The SVG image is built from three filled polygon faces, one white ellipse, and two white diagonal line segments. The three < polygon > elements define the black cube faces by connecting multiple coordinate points. The small white oval on the top face must be an < ellipse > because the markup uses cx, cy, rx, and ry; these attributes define an ellipse center point and horizontal/vertical radii. The diagonal marks on the left and right faces are straight segments, so they must use the SVG < line > element. A line is defined with starting coordinates x1, y1 and ending coordinates x2, y2. The first diagonal runs from the bottom point (200,365) to the upper-left point (50,100). The second diagonal must mirror it on the right side, so it starts at (200,365) and ends at (350,100). Therefore, the final coordinate selection is x2= " 350 " y2= " 100 " . References/topics: SVG shapes, < polygon > , < ellipse > , < line > , coordinate-based vector drawing, SVG markup construction.

< button onclick= " process() " > Process < /button >

< script >

function process()

{

}

< /script >

The button must use the onclick attribute because the required action occurs when the user clicks the button. The plain word click is an event name used in JavaScript event listeners, but it is not the correct inline HTML event-handler attribute. The value of the onclick attribute must be process() because the function must actually be invoked when the click event occurs. Using process alone only references the function name and does not call it in this inline markup context. this.process would attempt to reference a property on the current element, and javascript:process is not the correct handler expression. Inside the < script > block, the correct function declaration is function process(). This defines the named function that the button’s onclick attribute calls. The final structure therefore connects the button event directly to the script function: when the user clicks Process, the browser runs process().

< !DOCTYPE html >

< html >

< body >

< h1 > The Fitness World Around Us - Spring Conference < /h1 >

< form action= " process.php " method= " post " >

< legend > Conference Registration Form < /legend >

< p > < label for= " name " > Name: < /label >

< input type= " text " id= " name " size= " 30 " maxlength= " 30 " value= " " / > < /p >

< input id= " food " placeholder= " Cuisine " list= " food-choice " size= " 40 " / > < br >

< datalist id= " food-choice " >

< option value= " Vegetarian " > Vegetarian < /option >

< option value= " Traditional " > Traditional < /option >

< option value= " Surprise Me " selected > Surprise Me < /option >

< /datalist >

< input type= " submit " >

< /form >

< /body >

< /html >

The correct solution must satisfy all three stated form requirements. The title " Conference Registration Form " is supplied by the < legend > element in the first valid code segment. That same segment also includes the required attendee name field by using a < label > associated with an < input type= " text " > . The for= " name " and id= " name " relationship makes the label programmatically connected to the input, which is the correct HTML form-accessibility pattern. For the food options, the correct choice is the segment that uses an < input > element with a list attribute connected to a < datalist > element. This is required because the attendee must be able to select an option by using the mouse or type a value manually. A < select > element provides a fixed dropdown list, and radio buttons provide fixed clickable choices, but neither is the best match for a type-ahead list requirement. The < datalist > element supplies predefined options such as Vegetarian, Traditional, and Surprise Me while still allowing keyboard entry through the associated input field. References/topics: HTML5 forms, labels, text inputs, datalist, form usability, selectable and typed input options.

First box: minlength

Second box: maxlength

Third box: required

The correct validation attributes are minlength, maxlength, and required. The input must accept a category abbreviation that is either two or three characters long. The minlength= " 2 " attribute enforces the lower boundary by preventing submission when the entered text contains fewer than two characters. The maxlength= " 3 " attribute enforces the upper boundary by preventing the user from entering more than three characters into the field. Since the question states that the input is mandatory, the required attribute must also be included. required is a Boolean validation attribute, so it does not need a value; its presence alone makes the field required before the form can be submitted. Together, these attributes configure basic HTML5 constraint validation directly in markup without requiring JavaScript. The completed input therefore requires a value, rejects values shorter than two characters, and limits the value to no more than three characters. References/topics: HTML5 form validation, minlength, maxlength, required, text input constraints, mandatory form fields.