Free IT Specialist INF-306 Practice Exam with Questions & Answers

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.

==========

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

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.

display: grid;

grid-template-columns: repeat(6, 1fr);

grid-template-rows: 50px 50px 150px 150px 100px;

grid-gap: 10px 15px;

The correct grid definition starts with display: grid;, which turns the element into a CSS Grid container. To explicitly create six equal-width columns, the correct property is grid-template-columns, and the most efficient value is repeat(6, 1fr). The repeat() function avoids writing 1fr six separate times, while 1fr assigns each column one equal fraction of the available grid width. The five row sizes must be explicitly declared with grid-template-rows, using the exact varied values shown: 50px 50px 150px 150px 100px. This creates five rows with fixed pixel heights. For the spacing requirement, grid-gap: 10px 15px; is the correct shorthand. The first value controls the row gap, so rows are separated by 10px; the second value controls the column gap, so columns are separated by 15px. References/topics: CSS Grid containers, explicit grid tracks, grid-template-columns, grid-template-rows, repeat(), fractional units, grid gaps.

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.

==========

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.

The correct segment is D: filter: opacity(20%) drop-shadow(8px 8px blue);. The requirement says the image must have 80% transparency, which means only 20% opacity remains visible. The CSS filter property applies graphical effects to rendered elements, including image effects such as opacity adjustment and drop shadows. The opacity() filter function is valid inside filter, and values below 100% make the rendered element more transparent. The drop-shadow() function is also a valid CSS filter function and applies a shadow effect to the input image. Option A changes saturation, not transparency. Option B also changes saturation and incorrectly attempts to use box-shadow() as a filter function. Option C uses opacity(80%), which would produce 80% opacity rather than 80% transparency, and it also uses invalid box-shadow() syntax inside filter. References/topics: CSS filter property, opacity(), drop-shadow(), image effects, transparency.

==========

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.

==========

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 value is column-reverse. The flex-direction property defines the main axis of a flex container and determines whether flex items are laid out horizontally, vertically, or in the reverse direction. column creates a vertical layout where items flow from the top of the container toward the bottom. If new content is appended after existing content, normal column layout places that new item later in the visual list, typically lower on the page. column-reverse preserves a vertical main axis but reverses the visual direction, so later items in the source order appear at the highest visual point of the list. This satisfies the requirement without using the order property on individual flex items. row and row-reverse are incorrect because they create horizontal layouts, not vertical lists. The reverse-direction flex values should be used deliberately because visual order can differ from DOM order, but for this exam scenario, column-reverse is the value that places newly appended vertical content at the top. References/topics: CSS flexbox, flex-direction, main axis, column layout, reverse visual flow.

==========