Free Practice Questions for the IT Specialist Information Technology Specialist INF-306 Exam (2026 Updated)

First blank: < svg width= " 200 " height= " 200 " >

Second blank: < rect width= " 200 " height= " 200 "

Third blank: < circle cx= " 100 " cy= " 100 " r= " 50 "

Fourth blank: < /svg >

The correct solution uses SVG because SVG graphics are vector-based and can scale without pixel distortion when the page or viewport changes. A < canvas > element would require script-based drawing logic, which violates the requirement that JavaScript must not be required. An < img > or < picture > element can display an image, but those options do not define the rectangle and circle directly in markup. The outer container must therefore be < svg width= " 200 " height= " 200 " > . The blue square is created with < rect width= " 200 " height= " 200 " fill= " blue " / > , which produces a rectangle matching the required 200-by-200 dimensions. The centered white circle must use SVG circle geometry: cx= " 100 " and cy= " 100 " place the center at the midpoint of the 200-by-200 square, and r= " 50 " creates the required 50-pixel radius. The final closing tag must be < /svg > .

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 selections are B and C because both define a function as a member of an object context, which is the essential JavaScript pattern for declaring a method. MDN defines a method as a function that is a property of an object. It also shows that a function expression can be assigned to a variable or property and then invoked later. In option B, Score: function() { ... } represents an object-literal method property. This pattern is commonly used when defining custom objects, prototypes, configuration objects, or class-like structures in JavaScript. In option C, this.Score = function() { ... } assigns a function to the current object instance, creating an instance method that can be called through that object. Option A does not declare a method; as written, it is only an invalid or incomplete variable assignment and does not use the function keyword or method syntax. Option D invokes Score() and assigns its return value to a; it calls a function rather than declaring a method. References/topics: JavaScript custom classes, object members, function expressions, object-literal methods, instance methods.

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.

The correct answers are A and C because background-size: contain and background-size: cover are the CSS values that scale a background image in response to the size of the element or viewport. contain scales the background image as large as possible while preserving the entire image inside the background area. This prevents cropping and maintains the image’s aspect ratio, although empty space may appear if the container and image proportions differ. cover also preserves the aspect ratio, but scales the image until the entire background area is filled; this may crop part of the image, but it prevents empty space. Both values are commonly used in responsive design because the image automatically recalculates its rendered size as the page or element changes dimensions. initial resets the property to its default behavior and does not intentionally create responsive scaling. auto uses the image’s intrinsic dimensions or proportional automatic sizing, so it does not reliably adjust the graphic to different screen sizes in the way required. References/topics: responsive design, CSS background images, background-size, contain, cover, viewport-based scaling.

==========

The two likely causes are undersized touch targets and overlapping input regions. Touch input is less spatially precise than mouse input because the contact area of a finger is larger and less exact than a pointer cursor. Microsoft’s touch-target guidance states that interactive UI elements must be large enough for users to access accurately, and recommends a target size around 7.5 mm square, approximately 40 × 40 pixels on a 135 PPI display. Earlier Microsoft touch-design guidance similarly emphasizes that controls must be appropriately sized for touch and identifies approximately 9 mm as a minimum targeting area. Therefore, small input buttons may fail to trigger because the user is not actually hitting the active target area. Overlap is also a valid cause: when two active regions occupy the same physical screen area, hit testing may route the touch to a different element, or the effective target area may be reduced. W3C accessibility guidance explicitly treats overlapping targets as reducing measurable target size unless the overlapping controls perform the same action. Event handlers themselves are not the defect; they are the normal mechanism for processing input. “Touch screen not initialized” is not a standard HTML5 application cause. References/topics: touch input, event handling, hit testing, target size, overlapping controls.

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.

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.

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

==========

The correct markup uses the HTML5 < datalist > element because the interface shows a text input with a drop-down list of suggested values. The < input > element has list= " vehicles " , which means it must be connected to a < datalist > whose id value is exactly vehicles. This relationship is essential: the list attribute on the input references the id of the datalist that supplies the available options. Each < option > element inside the datalist defines one suggested value: Motorcycle, Truck, Boat, Car, and Bicycle. Unlike a traditional < select > element, a datalist does not restrict the user only to the listed choices; the user can either select an option with the mouse or type directly into the input field. That behavior matches the displayed interface, where the control appears as an editable text box with suggestions. The final closing tag must be < /datalist > because the option elements belong to the datalist container. References/topics: HTML5 forms, < input list > , < datalist > , option elements, selectable typed input.

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

First blank: class Dog extends Pet {

Second blank: super(name, breed);

The correct syntax for deriving one JavaScript class from another is extends, so the derived class declaration must be class Dog extends Pet {. This creates Dog as a subclass of Pet, allowing Dog instances to inherit members defined by the Pet constructor, including name, breed, and the show() function assigned inside the parent constructor. Inside a derived class constructor, super() must be called before using this. The call super(name, breed); invokes the parent Pet constructor and passes the values required to initialize the inherited name and breed properties. Pet(name, breed); is incorrect because a class constructor cannot be invoked like a normal function. Pet.constructor(name, breed); is also incorrect because it does not call the parent constructor for the current instance. After super() runs, the Dog constructor can safely assign subclass-specific properties such as price and gender. References/topics: JavaScript classes, inheritance, extends, derived constructors, super(), custom class creation.

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.

==========

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.

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.