Correct Answer:

Explanation:
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);.

Correct Answer:

Explanation:
First drop-down: datalist
Second drop-down: vehicles
Third drop-down: < /datalist >
The correct element is < datalist > because the interface requires a text input that provides selectable suggestions while still allowing the user to type. The < input > element uses list= " vehicles " , so it must be connected to a < datalist > element whose id is exactly vehicles. The id cannot be vehicle, because vehicle is already the input element's own identifier and does not match the value used by the list attribute. The < option
> elements inside the datalist define the suggested values: Motorcycle, Truck, Boat, Car, and Bicycle. ul, ol, and li are list-markup elements and do not create input suggestions. select would create a fixed dropdown list, but it would not match the editable input-with-suggestions behavior shown. The closing tag must match the opening datalist element, so the final selection is < /datalist > .

Correct Answer:

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

Correct Answer:

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