HTML5 Application Development INF-306 Exam Questions with Experts Answers Updated Recently

The correct transformation functions are matrix() and skew(). CSS transformations are applied with the transform property and accept transform functions that alter an element’s rendered appearance in two-dimensional or three-dimensional space. MDN defines < transform-function > as a data type representing a transformation that can rotate, resize, distort, or move an element in 2D or 3D space. The matrix() function is valid because it defines a homogeneous two-dimensional transformation matrix, allowing translation, scaling, rotation, and skewing effects to be represented numerically in one function. The skew() function is also valid because it explicitly skews an element on the 2D plane. scroll() is not a CSS transform function; scrolling is handled through overflow behavior or scrolling APIs. move() is also not a valid CSS transform function; the standard transform function for movement is translate(). References/topics: CSS3 transforms, transform property, 2D transformation functions, matrix(), skew().

==========

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.

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