IT Specialist INF-306 - HTML5 Application Development

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 valid selections are mouseup, scroll, and blur. A < canvas > element is represented by HTMLCanvasElement, which inherits from HTMLElement; therefore, it participates in the normal DOM event model for element-based interaction. mouseup is valid because it is fired on an Element when a pointing-device button is released while the pointer is over that element, which is a common canvas interaction pattern for drawing tools, games, drag tracking, and selection behavior. scroll is valid as an element event when an element is scrolled, and the HTML event-handler index lists onscroll for HTML elements. blur is also valid because it fires when an element loses focus; a canvas can participate in focus workflows, particularly when made focusable with attributes such as tabindex. play is excluded in this certification context because it is a media playback event associated with HTMLMediaElement behavior, not canvas graphics interaction. datareceived is not a standard HTML canvas or DOM event. References/topics: canvas DOM interaction, element event listeners, mouse events, focus events, scroll events.

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.

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 screen and (max-width: 480px) {

/* style rules go here */

}

The correct media query is @media screen and (max-width: 480px) {. The requirement says the style rule must apply to screen devices with a width of 480 pixels or less. In CSS media queries, screen identifies the media type, and (max-width: 480px) defines the upper viewport-width limit. This means the enclosed CSS rules apply when the viewport is 480 pixels wide or any smaller value, which is the standard mobile breakpoint behavior. @media screen and (width: 480px) is incorrect because it applies only when the viewport is exactly 480 pixels wide, not below it. @media screen display and (width: 480px) is invalid syntax because display is not used that way in a media query. @media screen-width: 480px is also invalid because it does not follow the required @media media-type and (feature: value) pattern. References/topics: responsive design, CSS media queries, @media, screen media type, max-width, mobile breakpoint styling.

Line 26 drop-down: 5

Line 29 drop-down: 8

Line 32 drop-down: 6

The groceries array starts empty. Line 24 runs fruits.shift(), which removes " Apples " from the fruits array. This leaves four fruits, but it does not add anything to groceries. Line 25 calls addVegetables(), which executes groceries = groceries.concat(vegetables);. Since vegetables contains five items, groceries contains 5 items at line 26. Line 27 then executes groceries.shift(), removing the first item from groceries and reducing the count to 4. Line 28 calls addFruits(), which appends the four remaining fruits, increasing the array count to 8; therefore, line 29 is 8. Line 30 executes groceries.pop(), removing the last item and reducing the count to 7. Line 31 executes groceries.shift(), removing the first item and reducing the count to 6. Therefore, line 32 is 6. The addOther() function on line 33 has not executed yet at the line 32 breakpoint. References/topics: JavaScript arrays, debugging breakpoints, concat(), shift(), pop(), push(), array item counting.

The correct features are saving temporary authentication tokens and passing form data to a confirmation page. sessionStorage provides a storage area scoped to the current origin and browser tab, and its data is retained only for the duration of the page session. That makes it appropriate for short-lived application state that must survive page reloads or navigation within the same workflow, but should not remain permanently available after the session ends. Passing form data from an entry page to a confirmation page is a classic session-scoped use case because the data is needed briefly during a multi-page transaction. Temporary authentication tokens can also fit the session-storage model when the token should be tied to the active browser session rather than persisted across future visits. Customized UI/UX settings usually need to persist across sessions, so localStorage or server-side user preferences are more appropriate. Game progress saved for future use is also persistent state, not session-only state. Passing data to a function is ordinary JavaScript memory usage and does not require Web Storage. References/topics: application state management, Web Storage API, sessionStorage, temporary workflow data, session-scoped tokens.

==========

The correct answer is D because the layout shown is a named-area CSS Grid layout. The mockup contains five semantic regions: the top header area for the logo and page title, a left-side menu, a central main content area, a right-side additional content area, and a bottom copyright/contact area. In CSS Grid, this type of visual structure is defined with grid-template-areas, where each quoted string represents one grid row and each repeated name represents how far that area spans across columns. In option D, heading spans the full top row, menu occupies the left column across the lower rows, content fills the main center region, right fills the additional content region, and contact spans the bottom row to the right of the menu. Option A only defines row and column sizes and does not name the five content areas. Options B and C are invalid for this purpose because named layout strings do not belong in grid-template-rows or grid-template-columns. References/topics: CSS Grid, grid containers, display: grid, named grid areas, grid-template-areas, page layout construction.

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.

==========