Free Practice Questions for IT Specialist INF-306 Exam

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.

==========

First drop-down: var xhr = new XMLHttpRequest();

Second drop-down: if(xhr.status===200){

Third drop-down: responseObject = JSON.parse(xhr.responseText);

The script must first create an XMLHttpRequest object, so the correct first selection is var xhr = new XMLHttpRequest();. This object performs the asynchronous request for menu.json. After the request finishes, the onload callback executes. The response should be processed only when the request succeeds, so the correct status check is if(xhr.status===200){; HTTP status 200 means the file was successfully retrieved. Status codes 403, 404, and 500 represent forbidden access, missing resource, and server error conditions, so they are not appropriate for normal JSON processing. The JSON file is returned as plain text through xhr.responseText, so it must be converted into a JavaScript object with JSON.parse(xhr.responseText). Once parsed, the code can access responseObject.menu[i].Entree, Price, and Description inside the loop and build the display output. responseXML is incorrect because the source file is JSON, not XML.

First blank: display: grid;

Second blank: grid-template-columns: auto auto auto auto;

Third blank: grid-gap: 10px;

The layout shown is a CSS Grid layout with eight items arranged into four equal-width columns and two rows. The first required declaration is display: grid;, which turns the .grid-container element into a grid container. The second declaration is grid-template-columns: auto auto auto auto;, which defines four columns, matching the four visible boxes in each row: Mickey, Minnie, Luna, and George on the first row, then Bilbo, Bella, Madeline, and Groucho on the second row. The third declaration is grid-gap: 10px;, which creates spacing between the grid cells, matching the visible blue gaps around each item. The background-color: #336699; creates the blue container background, while padding: 10px; adds space around the outer edge of the grid. The child rule .grid-container > div styles each grid item with a light background, centered text, padding, and larger font size.

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.

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.

The correct testing tasks are to verify application functionality, find defects, and ensure the app meets design specifications. Testing occurs after development produces a build and before acceptance or deployment decisions are made. Its purpose is to compare the implemented application against expected behavior, requirements, and design specifications. Option A is correct because functional testing confirms that user workflows, controls, validation rules, scripts, and page interactions work as intended. Option C is correct because defect discovery is a core testing responsibility; testers identify failures, inconsistencies, regressions, and unexpected behavior so the development team can correct them. Option D is correct because the app must be evaluated against the documented design, including layout, navigation, responsiveness, accessibility expectations, and feature behavior. Asking customers to submit bugs or feature requests is a feedback or product-management activity, not the primary task of an internal test cycle immediately following a development release. Checking syntax errors is primarily handled during development, linting, editing, or build processing; a released test build should already parse and execute sufficiently for functional testing. References/topics: application lifecycle management, test phase, defect detection, functional testing, design specification validation.

< 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().

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