IT Specialist INF-306 HTML5 Application Development Exam Practice Test

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.

First blank: < legend > Fundraising Campaign < /legend >

Second blank: < progress id= " donate " value= " 30 " max= " 100 " > < /progress >

Third blank: list= " donateAmount "

The correct answer is D because an SVG ellipse is created with the < ellipse > element and the required geometry attributes cx, cy, rx, and ry. The cx attribute defines the x-coordinate of the ellipse’s center point, and cy defines the y-coordinate of the center point. The rx attribute defines the horizontal radius, while ry defines the vertical radius. In option D, cx= " 200 " and cy= " 80 " correctly position the center of the ellipse, while rx= " 100 " and ry= " 50 " correctly define an ellipse that is wider than it is tall. Option A is invalid because the element name is misspelled as < ellipsp > , so the browser will not interpret it as an SVG ellipse. Option B incorrectly uses x and y attributes instead of the ellipse-specific center and radius attributes. Option C correctly uses cx and cy, but incorrectly uses x and y where rx and ry are required. References/topics: SVG markup, < svg > container, < ellipse > element, center coordinates, horizontal radius, vertical radius.

The correct element is animateTransform. In SVG, rotation is not produced by drawing a different shape; it is produced by applying a transformation to an existing graphical element, such as a < rect > representing a square. The < animateTransform > element is specifically designed to animate the transform attribute of a target SVG element, and its supported transformation types include translation, scaling, rotation, and skewing. Therefore, to rotate a square, the square would normally be defined with a shape element such as < rect > , and an < animateTransform > child or associated animation would specify attributeName= " transform " and type= " rotate " . animateMotion is incorrect because it moves an element along a motion path rather than rotating the element itself. circle is a shape element, not an animation mechanism. path defines arbitrary vector geometry, but it does not by itself animate or rotate another object. References/topics: SVG graphics, SVG transformations, animation elements, transform attribute, rotation animation.

==========

The correct method is arc(). In the Canvas 2D API, circles and circular arcs are drawn by creating an arc path on the canvas rendering context. MDN defines CanvasRenderingContext2D.arc() as creating a circular arc centered at (x, y) with a specified radius, start angle, end angle, and drawing direction. To draw a full circle, the common pattern is to call beginPath(), then arc(x, y, radius, 0, 2 * Math.PI), and then use stroke() or fill() to render the path. There is no standard Canvas 2D method named circle(), so option A is invalid. ellipse() can draw ellipses and can mathematically draw a circle if both radii are equal, but the classic and exam-targeted method for drawing a circle is arc(). bezierCurveTo() draws cubic Bézier curves and is used for custom curved paths, not the direct circle primitive. References/topics: Canvas 2D context, arc() method, drawing circles, radians, path rendering.

==========

Club Points indicator → < meter >

Order Status group title → < legend >

Choose delivery frequency options → < datalist >

Shipping Information group box → < fieldset >

Displayed shipping information → < output >

The correct semantic elements are selected according to the role each visible form component performs. The Club Points visual indicator represents a scalar measurement within a known range, so it corresponds to < meter > . The bordered Order Status section is a grouped form region, and the caption displayed on the border is a < legend > , which labels a fieldset-style group. The delivery frequency control shows an editable input with selectable predefined values, which is the purpose of < datalist > : it supplies suggested options for an associated input without forcing the user to choose only from the list. The Shipping Information section is visually and semantically a grouped set of related form information, so the surrounding grouping element is < fieldset > . The displayed shipping address is generated or presented as result-style information rather than typed directly in that location, which matches < output > . fieldset groups related controls, legend labels that group, meter displays a bounded measurement, datalist provides input suggestions, and output displays calculated or resulting information.

First drop-down: datalist

Second drop-down: vehicles

Third drop-down: < /datalist >

The correct element is < datalist > because the interface requires a text input that provides selectable suggestions while still allowing the user to type. The < input > element uses list= " vehicles " , so it must be connected to a < datalist > element whose id is exactly vehicles. The id cannot be vehicle, because vehicle is already the input element’s own identifier and does not match the value used by the list attribute. The < option > elements inside the datalist define the suggested values: Motorcycle, Truck, Boat, Car, and Bicycle. ul, ol, and li are list-markup elements and do not create input suggestions. select would create a fixed dropdown list, but it would not match the editable input-with-suggestions behavior shown. The closing tag must match the opening datalist element, so the final selection is < /datalist > .

pattern → Provides a way to set a regular expression that the value must match

placeholder → Provides a way to set default text that displays until focus is placed in an element

required → Provides a way to set form elements as mandatory

multiple → Provides a way to allow more than one file or email address in a single input

The correct matches are based on standard HTML5 form validation and input-attribute behavior. The pattern attribute defines a regular expression that the input value must satisfy before the form can be submitted successfully. It is commonly used for structured values such as phone numbers, codes, postal formats, or custom identifiers. The placeholder attribute supplies short hint text inside an input field, helping the user understand the expected value before entering data. The required attribute makes a form control mandatory; if the field is empty, constraint validation prevents successful submission. The multiple attribute allows a single input to accept more than one value, specifically for controls such as input type= " file " and input type= " email " , where users may upload multiple files or enter multiple email addresses. The maxlength attribute is not used in these matches because it limits the maximum number of characters that can be entered, but none of the listed descriptions asks for character-length restriction. References/topics: HTML5 form attributes, constraint validation, pattern, placeholder, required, multiple, input validation.

The correct segment is D because named grid-region layouts are defined with grid-template-areas. This CSS Grid property specifies named grid areas, establishes the cells in the grid, and assigns names to those cells. The syntax requires each row of the grid template to be written as a quoted string, with repeated names indicating that the named area spans multiple columns or rows. In the shown layout, heading spans the entire top row, menu occupies the left column across lower rows, content spans the central area, right occupies the right-side area, and contact spans the bottom content region. Options B and C are incorrect because named grid-area strings do not belong in grid-template-rows or grid-template-columns; those properties define track sizing, not named layout regions. Option A defines explicit column and row sizes but does not define the semantic named areas shown in the mockup. References/topics: CSS Grid, grid containers, named grid areas, grid-template-areas, responsive page layout.

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.

First drop-down: four

Second drop-down: maxlength

Third drop-down: email, password, and phone

The form contains four user-entry input elements: email, password, confirm password, and phone. Since the requirements state that all fields must be completed, the required attribute must be applied to all four inputs. The password field must prevent entries longer than eight characters, so the correct length-control attribute is maxlength, not max; max applies to numeric/date-style value ranges, while maxlength limits character count in text-style inputs. The phone field also benefits from maxlength because its placeholder format has a fixed visible structure. Finally, completed pattern attributes are needed for email, password, and phone because each has a required format rule: the email must match the placeholder-style address format, the password must use only letters and numbers, and the phone number must follow the placeholder format such as 123-45-678. The title attribute should accompany these patterns to produce meaningful browser validation messages.

Option C is the only segment that correctly combines three required pieces: two contributing < input > controls, a named < output > control, and executable form-level logic that assigns a calculated value into that output. The HTML < output > element is specifically designed as a container for the result of a calculation or user action, and its for attribute identifies the controls that contributed to the calculation by using a space-separated list of element identifiers or associated names in the form workflow. MDN’s reference demonstrates this exact pattern: two input values are added, and the result is assigned to an < output > element whenever input changes. Option A renders literal text inside < output > but does not update it. Option B has no < output > element at all, so it cannot satisfy the requirement. Option D declares an output but lacks an oninput handler or script assignment, so the displayed value never changes. References/topics: HTML5 forms, < output > element, for attribute, form input events, calculated form results.

==========

The correct answer is A because the code at line 03 creates an object by calling a constructor function with the new keyword. A constructor function must be declared with the same identifier used in the new Student( " David " , " Hamilton " ) expression. Inside the constructor, instance members should be assigned through this, because this refers to the newly created object. Option A correctly initializes this.firstname, this.lastname, and this.fullname, so beststudent.fullname is available at line 04 and evaluates to " David Hamilton " . Option B is invalid JavaScript syntax because var student(firstName, lastName) is not a valid function declaration. Option C is also invalid syntax for the same reason: var Student(firstname, lastname) cannot declare a constructor. Option D uses a valid function declaration, but it assigns firstname, lastname, and fullname without this, which creates or references non-encapsulated variables rather than properties of the constructed object. References/topics: JavaScript constructor functions, new keyword, object instance properties, this, custom classes.

The correct CSS is option B because the SVG filter is declared inside < defs > with the identifier id= " f2 " . To apply an SVG filter from CSS, the filter property must reference that filter by URL syntax using the filter’s ID selector: filter: url( " #f2 " );. The text selector targets the SVG < text > element, so the rule applies the defined filter effect to the visible text content, Blur Me!. The filter itself uses < feOffset > , < feGaussianBlur > , and < feBlend > to create the blurred visual effect. Option A is incorrect because filter: #blur; is not valid filter-reference syntax and does not match the actual filter ID. Option C is incorrect because fill controls paint color, not filter application, and blur is not a valid fill value. Option D uses url(blur), which does not reference the defined f2 filter and omits the required ID reference. References/topics: SVG filters, < filter > , filter IDs, CSS filter: url(#id), SVG < text > styling.

Media queries support responsive web design and allow different CSS rules to be applied at different screen sizes, device characteristics, or breakpoints. MDN describes media queries as a CSS mechanism for applying styles depending on media type and device or viewport characteristics, including width, height, resolution, and orientation. This is the foundation of responsive design because a page can adapt its layout for phones, tablets, laptops, and desktop displays without changing the HTML document. Breakpoints are the points where the design changes; MDN identifies them as the points where a media query is introduced to improve layout behavior across viewport sizes. Statement A is not generally correct because media queries are primarily a styling and layout mechanism, not a direct performance optimization. They can sometimes help avoid unsuitable layouts, but performance improvement is not their defining purpose. Statement D is incorrect because media queries are CSS rules; they do not execute or dynamically process JavaScript code. References/topics: responsive design, CSS media queries, viewport width, breakpoints, adaptive layout rules.

==========

Responsive layouts use CSS media queries to apply different style rules according to the viewport width or device characteristics. In this scenario, the three wireframes represent desktop, tablet, and mobile breakpoints. The desktop layout should use @media only screen and (min-width: 1025px) because desktop screens are the widest target group and begin above the tablet maximum width. The tablet layout should use @media only screen and (min-width: 481px) and (max-width: 1024px) because it covers the middle range between mobile and desktop. The mobile layout should use @media only screen and (min-width: 285px) and (max-width: 480px) because it targets the smallest viewport range shown in the available choices. The option @media only screen and (max-width: 1025px) and (min-width: 1920px) is logically invalid because a viewport cannot simultaneously be at least 1920 pixels wide and no more than 1025 pixels wide. References/topics: responsive web design, CSS media queries, viewport breakpoints, mobile layout, tablet layout, desktop layout.

< !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.

The correct markup is option D. The type= " tel " input type is appropriate for telephone-number entry, but it does not automatically validate a specific telephone-number format because phone formats vary internationally. MDN notes that tel inputs allow telephone entry but are not automatically validated to a particular format. Therefore, a pattern attribute is required to enforce the exact structure. The regular expression [0-9]{3}-[0-9] {3}-[0-9]{4} requires three digits, a hyphen, three digits, another hyphen, and four digits, matching the requested format such as 111-444-7777. MDN defines the pattern attribute as a regular expression the input value must match for constraint validation. The required attribute is also necessary because the field must not be empty; MDN states that required indicates the user must specify a value before the form can be submitted. Option A only limits length. Option B lacks hyphen validation and required. Option C hard-codes only specific digits. References/topics: HTML5 validation, tel, pattern, required, regular expressions.

==========

The correct answer is D because the pattern attribute requires the exact structure defined by the regular expression [a-zA-Z]{4}-[0-9] {2}-[0-9]{4}-[a-zA-Z] {4}. The first group, [a-zA-Z]{4}, requires exactly four alphabetic characters. The second group, [0-9] {2}, requires exactly two numeric digits. The third group, [0-9]{4}, requires exactly four numeric digits. The final group, [a-zA-Z] {4}, requires exactly four alphabetic characters. Hyphens must appear between each group. Option D, kukX-34-4938-WJDF, satisfies every part: kukX is four letters, 34 is two digits, 4938 is four digits, and WJDF is four letters. Option A fails because Uhj6 contains a digit in the final letter-only group. Option B fails because y7Ts contains a digit in the first group and A3 is not two digits. Option C fails because 23h contains a letter and breaks the two-digit group. References/topics: HTML5 input validation, pattern attribute, regular expressions, form constraint validation.

==========

Determine requirements → Develop code → Test the app

↓

Monitor performance ← Deploy the app

The correct application lifecycle sequence begins with Determine requirements because the team must first define what the app must accomplish, who will use it, and which functional and technical expectations must be satisfied. Since the question states that the design is already provided, the next implementation step is Develop code, where the HTML, CSS, JavaScript, assets, APIs, and app logic are created according to the approved design and requirements. After development, the app must be validated through Test the app. Testing confirms that the app works correctly, meets requirements, handles user input properly, and does not contain functional defects that would block release. Once testing is complete, the app can be released through Deploy the app, which publishes it to the target environment or makes it available to users. The final operational stage is Monitor performance, where the released app is observed, maintained, updated, and improved based on performance, reliability, defects, and user behavior. References/topics: application lifecycle management, requirements, development, testing, deployment, maintenance.