The Use Data JSON property must be selected in the properties of the Type Ahead Block in order to display the fetched data in the fields. The Lookup Mode property is used to specify the type of lookup to perform. The FirstName, LastName, and BirthDate fields can be placed inside or outside the Type Ahead Block. The typeHead key is in the correct format.

When testing a FlexCard data source in the designer, the developer must provide valid runtime values for context variables so the configured Integration Procedure can execute as it would at runtime. In this scenario, that means manually entering a valid Context ID, such as an Account record ID, in the Setup or Test Data Source settings and then viewing the returned data. Without a valid context value, the Integration Procedure may not receive the input required to query Account, Opportunity, and Case data. Option C is important inside the Integration Procedure design, but the question asks about testing the FlexCard's data configuration in the designer. Option B is not generally required for SOQL. Option D is a design choice, not the key testing step.

According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: AccountName, AccountNumber, AccountType, AccountOwner, ContactName, and ContactPhone.
The DRGetAccountDetails action is a DataRaptor Extract action that retrieves data from the Account and Contact objects in Salesforce. The BlkContacts element is a Repeat Block that displays a list of contacts related to the account. Therefore, the JSON from the DRGetAccountDetails action that would display all six values correctly in the OmniScript structure shown is option C, which has the following structure:
{ The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

The missing access is execute access to the specific Apex class used by the Remote Action. A Remote Action in an Integration Procedure invokes Apex or an invocable action, so the running user must be authorized to execute that Apex class. Salesforce documentation for OmniStudio Apex class permission checkers states that access must be enabled for the classes used by Remote Action APIs for each profile, permission set, or permission set group. "Run Flows" is irrelevant because this is not Flow execution. General data-model access may still be required for object operations, but it does not authorize the Apex class itself. A Try-Catch Block can catch or handle an error response, but it does not fix the underlying unauthorized Apex execution failure.

The verified answer is C. The selected answer in the PDF appears to be wrong. For OmniStudio managed package runtime, upgrades are package-based and can require installing the newer managed package version.
Salesforce documentation for installing or upgrading the OmniStudio package says to install the latest OmniStudio managed package by going to OmniStudio Managed Package Releases and using the installation URL. That is different from standard runtime behavior, where functionality is more directly tied to Salesforce platform releases. Option D incorrectly treats managed package runtime as automatically upgraded only through seasonal Salesforce releases. Option A is wrong because a support case is not the normal upgrade mechanism. Option B overstates the process; deactivating all components is not the defining characteristic.