C_BASD_01 SAP Certified Development Associate - Build applications with SAP Business Application Studio Questions and Answers

The correct way for an application developed on SAP Business Application Studio to use data directly from a back-end system is to consume an external data service. This can be done by using the Service Center in SAP Business Application Studio, which simplifies the connectivity to external data sources, enables data source exploration from different providers, and integrates the data source into the application in development. For example, you can consume an external service from SAP S/4HANA by adding the Business Partner API to your application and adding the Business Partner entity to your application service. References:

• Connect to External Data Sources with SAP Business Application Studio
• Consuming an External Service From SAP S/4HANA - SAP Learning

There are two different options for adding sample data in SAP Business Application Studio1:

• Import for Entity: This option allows you to import sample data from a CSV file for a specific entity. You can use this option if you have a predefined set of data that you want to use for testing or demonstration purposes. You need to download the CSV file from a source, rename it to match the project and entity names, and then select the Import for Entity option from the Add Sample Data dialog. You can then choose the file and import it to the entity.
• Create for Entity: This option allows you to create sample data manually for a specific entity. You can use this option if you want to enter your own data or generate mock data for testing or demonstration purposes. You need to select the Create for Entity option from the Add Sample Data dialog, and then enter the number of rows and the values for each property. You can also turn on the Mock Data option to automatically generate random values for each property.

You do not have the following options for adding sample data in SAP Business Application Studio:

• Import for Service: This option does not exist in SAP Business Application Studio. You cannot import sample data for a service, but only for an entity. A service is a logical grouping of entities that exposes them as an OData API. You can only import sample data for each entity individually.
• Create for Service: This option does not exist in SAP Business Application Studio. You cannot create sample data for a service, but only for an entity. A service is a logical grouping of entities that exposes them as an OData API. You can only create sample data for each entity individually.

References:

• 1: Adding Sample Data - SAP Learning

To run your application with live data, you need to do the following steps:

• In the target run configuration to run with, configure the data source as “Live Data”. This will enable your application to consume external OData services from their original sources, instead of using mock data from the sample data folder1.
• In the target run configuration to run with, configure the destination of OData service properly. For each OData service, you must specify the target configuration that refers to the external OData service: BTP destination name and an optional path to the service endpoint2.

You do not need to delete any existing run configurations that do not have “Live Data” chosen as data source, as they can be useful for testing your application with different scenarios. You also do not need to rename the target run configuration to run with, to make sure it contains “Run with Live Data” text, as the name of the run configuration does not affect its functionality.

References:

• 1: Previewing Your Application - SAP Learning
• 2: The fastest and easiest way to run full-stack applications in SAP Business Application Studio | SAP Blogs

Using SAP Business Application Studio, you use the Deploy action to upload your application to Cloud Foundry. The Deploy action allows you to build and deploy your application to the Cloud Foundry runtime environment. You can use the Command Palette tool or the Terminal in SAP Business Application Studio to perform this action. You need to have a valid Cloud Foundry account and a configured manifest file for your application12

References: 1: Deploying an Application to Cloud Foundry | SAP Help Portal 2: Deploying an Application to SAP Mobile Services | SAP Help Portal

To run a CI/CD build manually without pushing changes to Git, you can select ‘Trigger a Build’ in the CI/CD job’s context menu. This will start a new build for the selected job, using the latest code from the remote Git repository. You can see the build status and logs in the CI/CD view in SAP Business Application Studio. The other options are not correct, because they either require pushing changes to Git (B), or they do not use the CI/CD service (A and D). References:

• Managing the Application’s Lifecycle with CI/CD Service

 You can use CI/CD job webhook data to automatically trigger a build for that CI/CD job whenever someone pushes changes to the repository. A webhook is a way of notifying a service about an event that occurred in another service, such as a code change in a Git repository. By configuring a webhook between your repository and SAP Continuous Integration and Delivery, you can automate your builds and ensure that your application is always up to date with the latest code changes. The other options are not correct, because they are not the purpose of CI/CD job webhook data. To email you whenever changes are pushed to the repository, you can use the notification settings in your Git service. To automatically sync your local repository whenever changes are pushed to the repository, you can use the pull command in the terminal or the Sync & Share action in the Project Explorer. References:

• Managing the Application’s Lifecycle with CI/CD Service
• SAP Help Portal
• Introduction to SAP Continuous Integration and Delivery service for SAP …

When you create a CI/CD job for a low-code project, such as an SAP Fiori elements project, you can choose from two options in the Release stage: Deploy to Cloud Foundry or Deploy to Cloud Transport Management Service. Deploy to Cloud Foundry allows you to deploy your application to a Cloud Foundry environment in SAP BTP. Deploy to Cloud Transport Management Service allows you to deploy your application to different subaccounts using the Transport Management service in SAP BTP. References:

• SAP Help Portal
• Managing the Application’s Lifecycle with CI/CD Service - SAP Learning

You use the Page Editor tool to add a value help UI to section fields on the Object Page of an SAP Fiori elements application. The Page Editor is a graphical user interface that allows you to configure and customize the UI elements of your application using annotations. You can access the Page Editor from the Application Information page or the Command Palette tool in SAP Business Application Studio12

To add a value help UI to a section field, you need to follow these steps:

• Open the Page Editor for the Object Page of your app and expand the nodes Sections->Section Name->Subsections->Field Group Name->Form.
• Select the field that you want to add a value help UI to and open the Property Sheet.
• In the Property Sheet, scroll down to the Value Help section and enable the Value Help switch.
• Choose the Value Help Type from the drop-down list. You can choose from Basic, OData, or Custom.
• Depending on the Value Help Type, you need to provide additional properties, such as the Value List Entity, the Value List Path, the Value List Parameters, or the Custom Value Help Function34

References: 1: Page Editor | SAP Help Portal 2: Create an SAP Fiori Elements Application | SAP Tutorials 3: Value Help | SAP Help Portal 4: Fiori Elements – How to Develop an Object Page | SAP Blogs

 To access the data in your application, you need to have the appropriate role collection assigned to your user. A role collection is a set of user-related authorizations that restrict access to resources and services based on defined user permissions. You can create a new role collection for your application in the SAP BTP subaccount cockpit, or use an existing one that matches your application’s requirements. Then, you need to assign the role collection to your user via the SAP BTP subaccount cockpit, so that you can access the data in your application. Redeploying the project or logging out and in again will not solve the issue, as the rolecollection assignment is independent of the deployment or the login process. References:

• Manage Authorizations and Roles
• Manage Role Collections

You can find Microsoft Visual Studio Code compatible extensions for a dev space in the Open VSX Registry. The Open VSX Registry is a vendor-neutral open-source alternative to the Visual Studio Marketplace. It hosts a variety of extensions that can enhance the functionality and usability of your dev space. You can explore and install extensions from the Open VSX Registry using the Extensions view in SAP Business Application Studio12

References: 1: Explore and Install VS Code Extensions | SAP Help Portal 2: Introducing SAP Business Application Studio (BAS)

Project sharing is a feature of SAP Business Application Studio that allows you to share your project with other developers via a remote Git repository. Git is a distributed version control system that lets you track changes and collaborate on code. SAP Business Application Studio supports Git as the source control management tool for project sharing. You can use the Simplified Git view or the Source Control view to perform Git operations such as clone, commit, push, pull, merge, and so on. You can also use the terminal to execute Git commands. You can connect to any public or private Git service provider, such as GitHub, GitLab, or Bitbucket, as well as your corporate Git system. Project sharing via Git enables you to work on the same project with other developers, synchronize your changes, and resolve conflicts. References: Sharing the Project via Git | SAP and Git Source Control | SAP Help Portal

The correct developer flow for consuming an external data source in your application is to add an external data source from the storyboard, add the data model to the application, add a service from the storyboard, add a new lead entity to the service, and add a relationship to the external data source entity. This flow allows you to explore the external data source in the Service Center, select the relevant entities and fields, and integrate them into your application model. You can also create a user interface for the external data source using SAP Fiori elements. References:

• Consuming an External Data Model
• Connect to External Data Sources with SAP Business Application Studio

When you add a new projection to your project, you are creating a new service that exposes a view on underlying domain model entities. A projection is a CDS data definition that defines a subset of fields or a join of entities from the domain model. A projection can also apply filters, aggregations, or calculations on the data. A projection is used to expose data to the service layer or the user interface layer1. A projection is not an external data model, a data model entity, or a user interface application.

References:

• 1: CDS Data Definitions - SAP Learning

The number of runtime units required for a full-stack application depends on various factors, such as the performance, scalability, and availability of your application. Some of the factors that help you determine the number of runtime units are12:

• Number of users involved: This factor indicates how many concurrent users are expected to access your application at any given time. The more users you have, the more load your application will generate, and the more runtime units you will need to handle the requests and responses.
• Volume of data handled by your application: This factor indicates how much data your application needs to store, process, and transfer. The more data you have, the more memory and disk space your application will consume, and the more runtime units you will need to support the data operations.

You do not need to consider the following factors to determine the number of runtime units:

• Number of UI applications deployed: This factor indicates how many UI modules you have in your full-stack application. The number of UI applications does not directly affect the number of runtime units, as the UI applications are served by a web server that is independent of the runtime units. However, the number of UI applications may affect the complexity and size of your application, which may in turn affect the performance and scalability of your application.
• Number of services deployed: This factor indicates how many service modules you have in your full-stack application. The number of services does not directly affect the number of runtime units, as the services are deployed as separate applications that can be scaled independently. However, the number of services may affect the communication and integration between your application components, which may in turn affect the performance and availability of your application.

References:

• 1: SAP Business Application Studio - Trial Account Restrictions
• 2: Cloud Foundry Environment - SAP Help Portal

 When you create a CVCD job, you need to define the SCM credentials for your project. This enables the CVCD service to access your project from the SCM repository and retrieve the latest version of your code when the build is triggered. The SCM credentials are stored securely in the CVCD service and are not exposed to anyone. References: Managing the Application’s Lifecycle with CI/CD Service - SAP Learning