IT Specialist INF-306 Dumps

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 blank: < legend > Fundraising Campaign < /legend >

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

Third blank: list= " donateAmount "

Application Lifecycle Management organizes website creation into ordered stages that move from intent to implementation and long-term support. The Plan stage comes first because it establishes why the website exists, who the audience is, and what goals the application must satisfy. The Design stage converts those requirements into structure, including page layout, navigation, interface organization, and visual arrangement. The Develop stage is where the website is built by writing HTML markup, CSS styling, JavaScript behavior, and integrating required assets or APIs. The Test stage evaluates whether the completed website functions correctly and is usable according to requirements; this includes checking features, layout behavior, validation, and user workflows. The Deploy stage publishes the finished website to the target hosting or production environment so users can access it. Finally, the Maintain stage occurs after release and includes monitoring, updating, fixing defects, improving compatibility, and keeping content or functionality current. References/topics: application lifecycle management, planning, design, development, testing, deployment, maintenance.

The paragraph containing the text Tigers will display first.

False

The section p CSS refers to the parent flexbox container.

False

When the paragraphs have a width less than 200px, the last paragraph will wrap to the next line.

True

The parent flexbox container is the section element because it has display: flex;. The paragraphs inside the section become flex items. The display order is controlled by each paragraph’s inline order value, and flex items are laid out from the lowest order value to the highest. Therefore, Zoo Trip with order: 1 displays first, followed by Bears, Lions, and finally Tigers; the statement that Tigers displays first is false. The selector section p does not refer to the parent flexbox container. It targets paragraph elements inside a section, meaning it styles the flex items, not the flex container. The container itself is targeted by the section rule. The final statement is true in intent because flex-wrap: wrap; allows flex items to move to a new line when they cannot fit in the available row. Since each paragraph has min-width: 200px, items are prevented from shrinking below that minimum and wrapping occurs when available space is insufficient. References/topics: CSS flexbox, flex container, flex items, order, flex-wrap, min-width.

The correct causes are insufficient input target size and overlapping input areas. Touch interaction depends on hit testing: the browser or platform determines which element occupies the touched screen coordinate and dispatches the event to that element. If a button’s active area is too small, the user’s finger may visually appear to tap the button while the actual touch coordinate falls outside the actionable target. Microsoft’s touch-target guidance recommends touch targets around 7.5 mm square, approximately 40 × 40 pixels on a 135 PPI display, to support reliable activation. Overlap is also a valid cause because one element can partially cover or compete with another during hit testing; W3C target-size guidance notes that overlapping areas should not be counted as usable target area unless the overlapping controls perform the same action. Event handlers are not the problem by themselves; they are the standard mechanism for detecting user input. “Touch screen not initialized” is not a normal HTML5 application-level cause. References/topics: touch input, event handling, hit testing, target size, overlapping controls.

==========

The correct method is preventDefault(). In an HTML form submission workflow, the browser’s default action is to submit the form, which commonly navigates away from the current page or reloads it. Calling event.preventDefault() inside the form’s submit event handler cancels that default action, allowing the current form state to remain visible while custom validation logic displays error messages. MDN defines preventDefault() as the method that cancels the default action normally taken by the implementation for that event. The submit event is the correct event context because it fires when the form submission is triggered. defaultPrevented is only a Boolean property indicating whether cancellation has already occurred; it does not cancel anything. cancelable only reports whether an event can be canceled. abort is not the correct form-validation event method. References/topics: HTML5 form validation, custom validation messages, submit event handling, event cancellation, preserving user input.

==========

< input id= " phone "

pattern= " [0-9]{10} "

placeholder= " 0000000000 " >

The correct first attribute is pattern because the requirement is to validate the entered value against a specific format: exactly ten numeric digits and no symbols. The regular expression [0-9]{10} means that only digits from 0 through 9 are allowed, and exactly ten of them must be entered. This prevents values such as 123-456-7890, (123)4567890, or 123 456 7890 because those contain symbols or spaces. The correct second attribute is placeholder, not value, because the input should initially display all zeroes but that displayed text must not be submitted or stored with the form. A placeholder is hint text shown when the field is empty; it disappears when the user enters real data and is not submitted as the control’s value. By contrast, value= " 0000000000 " would actually prepopulate the input and could be submitted if the user did not change it. The required option is not selected because the question focuses on format validation and display hint behavior, not mandatory completion. References/topics: HTML5 form validation, pattern, regular expressions, placeholder, input constraint validation.

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.

A CSS flexible box layout is created by applying the display property to a container with either flex or inline-flex. This establishes the element as a flex container and causes its child elements to become flex items. The flex-direction property defines the direction of the main axis and accepts row, row-reverse, column, and column-reverse, allowing items to flow horizontally, vertically, or in reverse order. The align-items property controls how flex items are aligned along the cross axis, with values such as flex-start, flex-end, and center. The direction property controls writing direction and accepts ltr for left-to-right text flow or rtl for right-to-left text flow. Finally, order is applied to individual flex items and accepts an integer value, represented here as “any,” because any numeric order value can be used to rearrange item display order without changing the document source order. References/topics: CSS flexbox, flex containers, flex items, main axis, cross-axis alignment, writing direction, item ordering.

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.

First drop-down: flex boxes

Second drop-down: background-size

Third drop-down: cover

The correct layout mechanism is responsive flex boxes because the content changes from a vertical mobile arrangement to a wider multi-column layout as space becomes available. Flexbox supports this behavior naturally through flexible item sizing and wrapping, often without needing explicit media queries for every screen size. The header image must fill its visible header region on both mobile and desktop. The correct CSS property for controlling how a background image scales inside its container is background-size. The correct value is cover, because background-size: cover scales the image so that the entire container is covered while preserving the image’s aspect ratio. This prevents distortion, although some cropping can occur when the image and container have different aspect ratios. contain would preserve the full image but may leave empty space. auto would use the image’s intrinsic size and would not reliably fill the header area. background-attachment, background-clip, and background-repeat do not control image scaling.

The first image has a brown/yellow vintage tone, which indicates the sepia(100%) CSS filter. Sepia converts the image colors into a warm monochrome effect commonly associated with aged photographs. The second image appears faded and washed out while retaining the same general image content, which corresponds to opacity(30%); this makes the image mostly transparent, allowing only 30 percent opacity. The third image shows the original beach image with a visible shadow offset behind it, so the correct filter is drop-shadow(8px 8px 10px black). The first two 8px values define the horizontal and vertical shadow offset, 10px defines the blur radius, and black defines the shadow color. saturate(100%) would leave saturation at its normal level and would not visibly create a special effect. grayscale(100%) would remove color entirely and produce a black-and-white image, which is not shown in the visible rows. References/topics: CSS filter property, image effects, sepia(), opacity(), drop-shadow(), graphical enhancement with CSS.

The correct answer is A. Applying float: right to an image removes the image from the normal inline flow and moves it to the right side of its containing block. Inline content, such as text, is then allowed to flow around the floated image. Because the image is anchored on the right, available text space is primarily on the left side of the image, and the text can continue above, beside, and below the floated region according to the surrounding layout. This is the classic use case for floating images within article-style content, where text wraps around a visual element rather than forcing the image to occupy an entire line. Option B is incomplete because it omits the important left-side wrapping behavior. Option C describes the opposite direction: an image floated left with text appearing to its right. Option D also describes float: left, not float: right. References/topics: CSS float, floated images, text wrapping, normal flow, content positioning.

==========

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.

==========

First drop-down: " click " ,

Second drop-down: moveElement,

Third drop-down: false,

The correct event listener syntax is addEventListener(type, listener, useCapture). The first argument must be " click " because the function must run when a button is pressed. The second argument must be moveElement, not moveElement(), because the event listener expects a function reference. Using parentheses would call the function immediately while the page is loading instead of waiting for the user to press a button. The third argument controls the event phase. false means the listener runs during the bubbling phase, which is the normal behavior for button click handling. true would register the listener for the capturing phase instead. Since the code uses document.querySelectorAll( " .item " ), it selects all elements with the class item. The for loop then attaches the same click listener to each selected button individually. This ensures that all four buttons invoke moveElement when clicked.

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.

==========

First blank: img

Second blank: filter:

Third blank: grayscale(100%)

Fourth blank: blur(8px)

The correct CSS selector is img because the requirement applies the visual effect to gallery images. The correct property is filter:, not transform:, because CSS filters modify the rendered appearance of an element using image-processing effects such as blur, grayscale, opacity, brightness, contrast, and shadows. The filtered sample appears blurred and colorless, so the appropriate filter functions are grayscale(100%) and blur(8px). grayscale(100%) removes all color from the image, converting it to a black-and-white rendering. blur(8px) obscures visual details, making the image difficult to recognize until the protected or authorized state changes the styling. The filter keyword without a colon is not a valid CSS declaration in this context. brightness(40%) and opacity(50%) could further obscure an image, but they are not required to reproduce the shown filtered result. The final declaration is therefore filter: grayscale(100%) blur(8px);.

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: navigator.geolocation

Second drop-down: navigator.geolocation

Third drop-down: getCurrentPosition(showLocation)

The correct API object is navigator.geolocation because browser-based geographic location is exposed through the Geolocation API, not through window.location. window.location represents the current page URL and navigation state; it does not provide latitude or longitude. The first selection checks whether the browser supports geolocation by evaluating navigator.geolocation. Inside the block, the same object must be used to request the user’s current position. The correct method is getCurrentPosition(showLocation), which requests the device’s current location and passes a position object to the callback function when the location is available. The callback then reads position.coords.latitude and position.coords.longitude and displays those values with alert(). The alternatives that pass window.location are incorrect because they provide page-location information rather than geographic coordinates. The alternatives that call showLocation(...) directly are also incorrect because the browser must first retrieve the actual position object. References/topics: Geolocation API, navigator.geolocation, getCurrentPosition(), callback functions, latitude and longitude.

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.