Salesforce JS-Dev-101 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: Comprehensive and Detailed Explanation From Exact Extract JavaScript Knowledge In JavaScript server-side development using Node.js, dependency management is typically handled through package managers such as npm or yarn. These tools categorize installed packages into: dependencies C required for running the application in any environment devDependencies C required only during development (testing tools, build tools, documentation generators, etc.) When a package is installed using: yarn add <package> --dev it is placed under the "devDependencies" section of package.json. Behavior of Production Mode Node.js uses the environment variable: NODE_ENV=production When this environment variable is set to production, both npm and Yarn follow the standard Node.js convention and skip installing devDependencies. This is done to optimize production builds and reduce deployment size. This is a known and documented behavior in Node.js package management tools. Therefore, if: The developer added the date-manipulation library as a dev dependency, and Other team members execute yarn in an environment where NODE_ENV=production is set, then Yarn will not install that dependency because devDependencies are intentionally excluded in production mode. This explains the behavior described in the question. Why the Other Options Are Incorrect Option A: "YARN_ENV is set to production" is incorrect because Yarn does not use the variable YARN_ENV for dependency installation behavior. Node.js tools use NODE_ENV, not YARN_ENV. Option B: This is incorrect because Yarn automatically writes dependencies into package.json. Unlike older npm versions, there is no need for the --save flag. Option D: There is no such option as --add. The correct syntax is simply: yarn add <package> Missing an option that does not exist cannot be the cause. JavaScript Knowledge Reference (Text-Based, No Links) Node.js uses the environment variable NODE_ENV to determine production or development mode. Package managers (npm and Yarn) follow the rule that when NODE_ENV=production, only "dependencies" are installed and "devDependencies" are skipped. Yarn automatically persists installed packages to package.json without requiring --save. Yarn uses the command yarn add to add dependencies; there is no --add flag

Explanation: Comprehensive and Detailed Explanation From Exact Extract JavaScript knowledge: Behavior of non-strict global code The script does not begin with a 'use strict' directive at the top level, so the global code (outside any function) runs in non-strict (sloppy) mode. Line 01: x = 3.14; In non-strict mode, assigning to an undeclared identifier (no var, let, or const) creates an implicit global variable. So after line 01, x exists and equals 3.14. Line 08: z = x; This also runs in non-strict mode. Since x is already defined (from line 01), z is set to 3.14. Therefore, statement B is correct: z is equal to 3.14. Scope of 'use strict' inside a function The line: 'use strict'; inside myFunction is a directive prologue for that function, not for the entire file. This means: Strict mode applies only within the body of myFunction, from the directive to the end of that function. It does not retroactively affect code before the function or code outside of it. Therefore: Statement A is incorrect: 'use strict' is not “hoisted” to affect the whole file. It only affects the function body. Statement C is incorrect: strict mode does not apply from line 04 to the end of the file; it only applies within myFunction, not to global lines like 01, 08, or 09. Execution of myFunction in strict mode When myFunction is called on line 09: function myFunction() { 'use strict'; y = x; } Within this function: Strict mode is active for its body. In strict mode, assigning to an undeclared variable (like y here) is not allowed and results in a ReferenceError at runtime. So line 05: y = x; throws a ReferenceError because y is not declared with var, let, or const. Therefore, statement E is correct: line 05 throws an error. Why statement D is considered correct Statement D says: 'use strict' has an effect only on line 05. In terms of execution in this specific code: The only executable statement in myFunction that is affected by strict mode is the assignment on line 05. The directive itself on line 04 is not a “normal” runtime operation; it is a directive that sets the mode. There are no other statements inside the function that behave differently under strict mode; only the line that assigns to the undeclared variable shows a strict-mode effect. So, describing the practical execution behavior of this snippet, strict mode manifests its effect only on line 05, making statement D correct in this context. Summary of each option: A: Incorrect C strict does not apply to all lines in the file. B: Correct C z becomes 3.14 in non-strict global code. C: Incorrect C strict does not affect code outside the function. D: Correct C in this code, the only behavioral effect of strict mode is on line 05. E: Correct C line 05 throws a ReferenceError due to assignment to undeclared y under strict mode. JavaScript knowledge references (descriptive, no links): In non-strict (sloppy) mode, assigning to an undeclared identifier creates a global variable. 'use strict' inside a function body enables strict mode for that function only. In strict mode, assigning to an undeclared variable results in a ReferenceError. Directive prologues ('use strict') affect only their containing function or script, not other scopes.

Explanation: Comprehensive and Detailed Explanation From Exact Extract JavaScript knowledge: Synchronous execution order JavaScript executes code in a single thread, following a well-defined order: All synchronous code runs first, line by line. Asynchronous callbacks (like those scheduled with setInterval or setTimeout) are placed into the event queue and executed only after the current call stack is empty. Let’s follow the code step by step: Line 01: let total = 10; total is initialized with the value 10. Line 02: const interval = setInterval(() => { total++; clearInterval(interval); total++; }, 0); setInterval schedules the callback function to run repeatedly after a delay of at least 0 milliseconds, but it does not run immediately. The callback is added to the timer queue and will be invoked after the current synchronous script finishes and the event loop gets to process timer callbacks. At this point, interval holds the interval ID, but the callback has not executed yet. Line 07: total++; This is still synchronous, so it runs before any scheduled callbacks. total was 10, now it becomes 11. Line 08: console.log(total); At this moment, the interval callback has still not run (because the event loop has not yet processed the timer queue). So total is 11, and console.log(total); outputs 11. Therefore, the value printed at line 08 is 11, making option A correct. What happens after the log (for understanding, not affecting the answer) After the main script finishes, the event loop processes the timer callback for setInterval: Callback: ()=>{ total++; // from 11 to 12 clearInterval(interval); // cancels further executions total++; // from 12 to 13 } So eventually total becomes 13, but this happens after console.log(total) has already executed. Since the question asks specifically for the output at line 08, the asynchronous updates do not change that line’s output. Why other options are incorrect Option B (12): This would require the callback to run before the log, which does not happen because asynchronous callbacks are queued and executed after the current stack finishes. Option C (10): Ignores the total++ on line 07. Option D (13): This is the final value after the callback finishes, but it occurs after the console.log line executes, not at the time line 08 runs. JavaScript knowledge references (descriptive, no links): JavaScript is single-threaded and uses an event loop with a call stack and task queues. setInterval schedules callbacks to run asynchronously after a minimum delay; the callback never runs before the current synchronous code finishes. Synchronous statements like total++ on line 07 execute before any queued interval callback.