programming languages Online Quiz - 73

Workflow persistence refers to saving the runtime state of a workflow instance to any durable storage medium (persistence store) so it can be resumed later. While databases are commonly used, persistence is not strictly limited to databases, making the broader definition correct.

State Machine workflows were NOT available in the initial WF4.0 release (.NET Framework 4.0). They were reintroduced in WF4.5 (.NET Framework 4.5). The initial WF4.0 release included Flowchart, Sequence, and other activity types, but not State Machine. The claimed answer 'False' is correct for WF4.0 specifically.

Bookmarks in WF4.0 are a mechanism that allows an activity to pause its execution at a specific point and wait for an external event to resume it. The activity 'hangs' (waits) at the bookmark position until ResumeBookmark is called with matching bookmark name. Bookmarks enable long-running workflows that can wait for user input or external events without blocking threads.

StateInitialization is a WF3.0 activity that was NOT carried forward to WF4.0. In WF4.0, state machine workflows were completely absent initially and when reintroduced in WF4.5, they use different activity types (State, Assign, etc.). The other options (WriteLine, Assign, Flowchart) are all valid built-in WF4.0 activities.

In WF 4.0, the available control flow constructs are FlowChart and Sequence activities. StateMachine was not part of the initial WF 4.0 release - it was reintroduced later in WF 4.5. The other options incorrectly include StateMachine or don't list both available types.

WF 4.0 and WCF are distinct .NET technologies that can work together but are not integrated into a single framework. WF handles workflow orchestration while WCF handles service communication. They can be used together (e.g., WF workflows can call WCF services), but they remain separate technologies.

WF 4.0 workflows cannot automatically continue execution in a different system or project. Once a workflow starts, its activities execute within the same workflow application context. While workflows can communicate across systems (e.g., via WCF), the workflow instance itself cannot be transferred to run in another system or project mid-execution.

The Pick activity in WF 4.0 is specifically designed for event-driven scenarios. Each branch in a Pick contains a Trigger activity (like ReceiveEvent) that waits for a specific event, and an Action activity that executes when that event occurs. This makes Pick the primary event-handling construct in WF 4.0.

To access InArgument values within a custom activity's Execute method in WF 4.0, you have two correct approaches: either use context.GetValue(inArgument) or call inArgument.Get(context). Both methods require the ActivityContext parameter to resolve the argument's value at runtime. Simply referencing the argument by name or calling Get() without context will not work.

WF 4.0 provides three main hosting options: WorkflowInvoker for synchronous execution (simplest), WorkflowApplication for advanced scenarios with persistence/bookmarks/lifecycle control, and WorkflowServiceEndpoint for WCF integration. WorkflowRuntime is from the older WF 3.x and is not used in WF 4.0.

innerHTML, innerText, outerHTML, and outerText are properties of DOM Element objects, not methods. They are accessed like element.innerHTML (without parentheses), not invoked as functions. Methods would be called with parentheses.

innerHTML is a property of DOM elements, not a method. It should be accessed as document.getElementById('trial').innerHTML (without parentheses), not innerHTML(). The parentheses would attempt to call it as a function, which is incorrect syntax.

In JavaScript, functions are first-class objects and can be assigned to variables, meaning the language treats function names and variable identifiers within the same scope namespace rules.

HTTP status code 200 OK indicates a successful request. 304 is Not Modified (cached), 404 is Not Found (error), and other 4xx/5xx codes indicate errors. 200 is the standard success response for GET, POST, and other successful HTTP requests.

onreadystatechange is a PROPERTY (event handler) of XMLHttpRequest, not a method. You assign a function to it: xhr.onreadystatechange = function() { ... }. It's called when the readyState changes, but you don't invoke it as a method like xhr.onreadystatechange().

The open method of the XMLHttpRequest object takes the HTTP method as its first argument, and 'POST' is a valid standard HTTP method alongside 'GET'. Therefore, POST requests can indeed be sent using this method by passing 'POST' as the first parameter followed by the target URL.

XMLHttpRequest (XHR) requests are AJAX calls that fetch data asynchronously without reloading the page. These requests do not create new history entries - only page navigation through hyperlinks, window.location, or form submissions add to browser history. Therefore, the statement is false.