Explanation:
This question tests your knowledge of Semantic Versioning (SemVer), a versioning scheme used for software packages. SemVer uses a three-part version number: MAJOR.MINOR.PATCH. The rules are: increment the MAJOR version for incompatible API changes, increment the MINOR version for backward-compatible new features, and increment the PATCH version for backward-compatible bug fixes. The previous version is 1.1.3. Since the new features do not break backward compatibility, the MINOR version should be incremented, and the PATCH version should be reset to 0. Therefore, the new version is 1.2.0.

Correct Option:
D. 1.2.0 –
Correct. The previous version is 1.1.3. Adding new features that are backward-compatible means incrementing the MINOR version (from 1 to 2) and resetting the PATCH version to 0. The MAJOR version remains 1 because there are no breaking changes. The new version is 1.2.0.

Incorrect Options:

A. 1.2.3 –
Incorrect. This increments the MINOR version but keeps the PATCH version at 3. According to SemVer, when you increment the MINOR version, the PATCH version should be reset to 0. Keeping it at 3 is incorrect.

B. 1.1.4 –
Incorrect. This increments the PATCH version, which is used for bug fixes, not for new features. Adding new features requires a MINOR version increment, not a PATCH increment.

C. 2.0.0 –
Incorrect. This increments the MAJOR version, which is reserved for backward-incompatible API changes. Since the new features do not break backward compatibility, the MAJOR version should not change.

Reference:

Semantic Versioning (SemVer) Specification – semver.org

npm Documentation – Semantic versioning and package updates

MDN Web Docs – Semantic versioning for packages

Salesforce Trailhead – JavaScript Essentials: Managing Packages and Versioning

Explanation:
This question tests your understanding of the JavaScript event loop, async/await, setTimeout, and the order of execution of synchronous and asynchronous code. Synchronous code runs first, so console.log(4) and console.log(5) execute immediately. Inside callDelay(), console.log(2) runs synchronously, then await delay(1000) is called. Inside delay, console.log(1) runs synchronously before setTimeout is scheduled. The await pauses callDelay, allowing the main thread to continue, so console.log(5) executes. After 1000ms, setTimeout resolves the promise, and console.log(3) executes. The final order is 4, 2, 1, 5, 3.

Correct Option:

A. 4 2 1 5 3 – Correct. Let's trace the execution step by step:

Line 14: console.log(4) executes synchronously → logs 4.

Line 15: callDelay() is invoked.

Inside callDelay, Line 09: console.log(2) executes synchronously → logs 2.

Line 10: await delay(1000) is called.

Inside delay:

Line 03: console.log(1) executes synchronously → logs 1.

Line 04: setTimeout(resolve, 1000) schedules a timer for 1000ms.

delay returns a pending Promise.

The await on line 10 pauses callDelay, and control returns to the main thread.

Line 16: console.log(5) executes synchronously → logs 5.

After 1000ms, the setTimeout callback resolves the promise, allowing callDelay to resume.

Line 11: console.log(3) executes → logs 3.

Final output: 4 2 1 5 3.

Incorrect Options:

B. 4 2 1 5 3 –
This is the same as option A, which is correct. (Duplicates in the question.)

C. 1 4 2 3 5 –
Incorrect. This suggests that console.log(1) logs before console.log(4), but console.log(4) is synchronous and runs before callDelay() is even called. console.log(1) runs inside callDelay(), which is called after console.log(4). The order is incorrect.

D. 4 5 1 2 3 –
Incorrect. This suggests that console.log(2) logs after console.log(5), but console.log(2) runs synchronously inside callDelay() before console.log(5) is reached. The order is incorrect because console.log(2) executes before the await pauses the function.

Reference:

MDN Web Docs – Event loop and asynchronous execution

MDN Web Docs – async/await and control flow

MDN Web Docs – setTimeout and timers

Salesforce Trailhead – JavaScript Essentials: Asynchronous Programming and Event Loop

Explanation:
This question tests your knowledge of DOM manipulation in JavaScript, specifically using getElementById() to select an element and modify its content. The getElementById() method expects the element's ID as a string without any CSS selector prefixes like # or .. Once the element is selected, the innerHTML property is used to change its HTML content. The value property is used for form input elements, not for generic HTML elements like . Therefore, the correct syntax is document.getElementById("status").innerHTML = 'Completed';.

Correct Option:

C. document.getElementById("status").innerHTML = 'Completed'; –
Correct. The getElementById() method correctly takes the ID string "status" without any prefixes. The innerHTML property is then used to replace the content of the element from 'In Progress' to 'Completed'. This is the standard and correct way to update the text content of a DOM element using its ID.

Incorrect Options:

A. document.getElementById(".status").innerHTML = 'Completed'; –
Incorrect. The getElementById() method does not accept CSS selector syntax like "." for classes. The string ".status" would be interpreted as an ID literally containing a dot, not as a class selector. Since no element has the ID ".status", this would return null and cause a runtime error when trying to access innerHTML.

B. document.getElementById("#status").innerHTML = 'Completed'; –
Incorrect. Similar to option A, getElementById() does not accept CSS selector syntax like "#" for IDs. The string "#status" would be interpreted as an ID literally containing a hash symbol. Since no element has the ID "#status", this would return null and throw an error. The # prefix is used with querySelector(), not getElementById().

D. document.getElementById("status").Value = 'Completed'; –
Incorrect. While the element selection part is correct, the property used is wrong. The value property is used for form elements like , , and , not for <span> elements. For a <span>, you must use innerHTML or textContent to change its content. The property name Value (with a capital V) is also incorrect case sensitivity; it should be lowercase value even if it were applicable.<br><br> <b>Reference:</b><br><br> MDN Web Docs – Document.getElementById() method<br><br> MDN Web Docs – Element.innerHTML property<br><br> MDN Web Docs – Node.textContent property<br><br> MDN Web Docs – HTMLElement.value property<br><br> Salesforce Trailhead – JavaScript Essentials: DOM Manipulation

Explanation:
This question tests your understanding of the Array.prototype.reduce() method and how to properly return the accumulated result from the reducer callback. The reduce() method expects the reducer function to return a value that becomes the new accumulator for the next iteration. In the given code, the reducer function on lines 03-05 is missing a return statement. Without a return, the function returns undefined for each iteration, causing the final result to be undefined (or NaN when added). To fix this, the reducer function must explicitly return the updated accumulator (e.g., return result + current; or return result += current;).

Correct Option:

D. 05 return result; –
Correct. The reducer function must return the accumulated value for the next iteration. On line 05, adding return result; ensures that the updated accumulator is returned after each iteration. The complete reducer would be (result, current) => { result += current; return result; }. This correctly returns the accumulated sum, and the reduce() method will return the final sum (with the initial value of 10).

Incorrect Options:

A. 03 if(arr.length == 0) { return 0; } –
Incorrect. This checks if the array is empty and returns 0, but this does not fix the missing return inside the reducer function. The reduce() method already handles empty arrays when an initial value is provided (it returns the initial value 10). Adding this check is unnecessary and does not address the core issue of the missing return inside the reducer.

B. 04 result = result + current; –
Incorrect. This changes the assignment syntax but still does not include a return statement. The reducer function still returns undefined because there is no explicit return. Without a return, the accumulator becomes undefined after the first iteration, leading to NaN or incorrect results.

C. 02 arr.map((result, current) => { –
Incorrect. This replaces reduce() with map(), which is not suitable for calculating a sum. map() returns a new array of the same length, not a single accumulated value. This would not produce the sum of the array elements and is the wrong method for this requirement.

Reference:

MDN Web Docs – Array.prototype.reduce() method

MDN Web Docs – Reducer callback return value

MDN Web Docs – Array.prototype.map() method

Salesforce Trailhead – JavaScript Essentials: Array Methods and Reduction

Explanation:
This question tests your understanding of ES6 module import syntax, specifically how to import a default export from a module. When a module exports a single default function, you can import it using the import statement with any name you choose, and then call it directly. The correct syntax is import printDate from '/path/DatePrettyPrint.js'; and then printDate(); to invoke the function. The default export does not need to be accessed as a property of an object; it is the default value of the module.

Correct Option:

D.

javascript
import printDate from '/path/DatePrettyPrint.js';
printDate();

This is correct. The module exports one default function. Using import printDate from ... imports that default export and assigns it to the variable printDate. Since it is a function, it can be invoked directly with printDate(). This is the standard way to import and use a default export.

Incorrect Options:

A. import DatePrettyPrint() from '/path/DatePrettyPrint.js'; printDate(); –
Incorrect. The import statement does not use parentheses for the imported value. import DatePrettyPrint() is invalid syntax. Additionally, printDate is not defined in the scope; the import is named DatePrettyPrint, not printDate.

B. import DatePrettyPrint from '/path/DatePrettyPrint.js'; DatePrettyPrint.printDate(); –
Incorrect. This imports the default export as DatePrettyPrint. However, the default export is a function, not an object with a printDate method. Calling DatePrettyPrint.printDate() would try to access a printDate property on the function, which does not exist, resulting in a TypeError.

C. import printDate from '/path/DatePrettyPrint.js'; DatePrettyPrint.printDate(); –
Incorrect. This imports the default export as printDate, but then tries to call DatePrettyPrint.printDate(). The name DatePrettyPrint is not defined because the import is named printDate. This would throw a ReferenceError because DatePrettyPrint is not declared.

Reference:

MDN Web Docs – import statement (default imports)

MDN Web Docs – export default

MDN Web Docs – Modules and default exports

Salesforce Trailhead – JavaScript Modules and ES6 Import Syntax