Pearson INF-306 New Attempt

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.

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.

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