Free Salesforce JavaScript-Developer-I Practice Exam with Questions & Answers | Set: 5

console.assert(condition, message?) logs an assertion error if condition is falsy.

To log an error when number + 2 === 0 is false, use:

console.assert(number + 2 === 0);

Other options are invalid or do not behave as described: console.error always logs, assert alone is not a built-in browser global, and console.classy doesn’t exist.

Node.js provides two built-in modules for creating servers:

http → creates non-secure HTTP servers

https → creates secure HTTPS servers

A secure server requires:

SSL/TLS certificates (key and cert)

The built-in Node.js module designed to handle these: https

Syntax for a secure server:

const https = require( ' https ' );

const fs = require( ' fs ' );

const options = {

key: fs.readFileSync( ' key.pem ' ),

cert: fs.readFileSync( ' cert.pem ' )

};

https.createServer(options, (req, res) = > {

res.write( ' Secure Server ' );

res.end();

}).listen(443);

Evaluation of options:

A is incorrect: No built-in module named secure-server exists.

B is incorrect: tls provides low-level TLS sockets, not HTTP/HTTPS servers.

C is incorrect: http only creates an insecure server.

D is correct: https is the built-in module required for secure web servers.

JavaScript Knowledge References (text-only)

Node.js exposes built-in modules http and https for server creation.

Secure servers require the https module, which supports TLS/SSL.

The tls module is lower-level and not used for full HTTP servers.

==================================================

Event-driven Node-style APIs expose events via .on(eventName, handler).

To listen for error events:

server.on( ' error ' , (error) = > {

console.log( ' ERROR ' , error);

});

A and B assume methods .error or .catch that don’t exist on typical event emitters.

C only catches synchronous errors from server.start(), not async event-based errors.

Comprehensive and Detailed Explanation From JavaScript/Node.js Knowledge:

In a Node.js project that uses package.json, you typically define a " start " script:

{

" scripts " : {

" start " : " node server.js "

}

}

Then you start the app with:

npm start

npm start:

Looks up the " start " script in package.json.

Runs the command defined there (commonly node server.js).

This is the standard way to start a Node.js app with npm-managed dependencies.

Why others are incorrect:

A. node start

Tries to run a file named start with Node; does not use package.json scripts.

C. npm start server.js

npm start does not take the script filename as an argument in this way; it just runs the start script as defined.

D. start server.js

Not an npm or node command; on some shells it just tries to “start” a process but is not the standard Node/npm workflow.

Relevant concepts: package.json, npm scripts, npm start, Node entry file execution.