C_FIORD_2404 Sample Questions Answers

index.html file

manifest.json file

OData annotation file

vocabulary.xml file

It creates connectivity by a reverse-invoke process on the on-premise system.

It supports custom destination API configuration and certificate inspection.

It secures an SSL tunnel between the SAP Cloud and the on-premise system.

It initiates a cloud-based reverse-invoke process.

It enables test-driven development.

It supports only synchronous requests.

It supplies higher level test doubles for timers and AJAX requests.

It provides support for spies, stubs and mocks.

View Modification

View Visibility

View Extension

View Replacement

Transactional

Legacy

Analytical

Factshest

Deploy to SAP Fiori launchpad

Deploy to SAP Cloud Platform

Deploy to SAPUI5 Java Repository

Deploy to SAPUI5 ABAP Repository

It never causes a test to fail

Testing across more than one page is NOT possible

End-to-end tests are NOT recommended.

The developer needs to create the test during development

Retrieve the token and send it with each write request

Execute the Refresh method for an expired token.

Include the token in the HTTP request body of each write request

Generate a token on each read and write request

POST

DELETE

PUT

get

Create an annotation file associated with the OData service and add annotations

Add catalog to user menu in a PFCG role and grant the role to user

Create a catalog, target mapping, and tiles

Choose the OData service as data provider for the project

App extension

Adaption extensions

ABAP extension

CDS extension

Use @UI.Iineitem.importance annotation to determine in which devices the field is displayed.

Use @UI.selectionField annotation to define a fuzzy search field

Use @Search.defaultSearchElement annotation to define input fields with value help.

Use @UI.hidden annotation to hide the fields that are not to be displayed on a list report

Sinon

QUnit

OPA

Mock server

Modify the runtime libraries that are to be loaded

Modify the properties of the view control

Modify the data model to merge data at runtime.

Enable merging of the standard and the custom controller at runtime.

Add custom view content in a predefined extension point.

Developing, Testing and Deploying

Ideation, Prototyping and Validation

Scoping, 360 degree research and Synthesis

Requirement gathering, Research and Documentation

/regions/companies/O/city

/regions/1/companies/l/city

/regions/0/companies/O/city

/region[0]/companies[O]/city

A nested structure for Sales Order and Sales Order Items.

A fat structure with Sales Order and Sales Order Items, and then add an expand command.

An object structure that defines the hierarchy.

An individual structures for both Sales Order and Sales Order Items, and then batch them.

Semi-dynamic

Dynamic

Static

Create a theme using the Theme Designer implementing the theme.

Create a model using the Web IDE implementing the theme

Reference the relevant artifacts in the bootstrap of the app.

Create a ess file using the Web IDE implementing the theme.

Create a module using the Web IDE implementing the theme.

Add a code snippet to check if the method exists and execute it

Create a ifile in the Util folder to allow the customer to add custom code.

Modify the bootstrap option to allow multi-layer extensions of the custom code.

Identify a strategic location in the controller for the customized code

Define a new function name ensuring itis reserved for the extension.

X:/regions/0/companies Y: name Z: city

X:/regions/companies Y: name Z: city

X:/regions/0/companies Y: companies/O/name Z: companies/O/city

X:/regions/companies Y: companies/name Z: companies/city

QUnit.module

This.calculator.press(wl");

eardown : function() {}

QUnit.test