C_BASD_01 Exam Dumps - SAP Certified Development Associate Certification Questions and Answers

To share your project with other users, you need to use a remote Git repository that can store and manage your project files. You can use any Git provider that you prefer, such as GitHub, GitLab, Bitbucket, etc. You need to push your project to the remote Git repository and share the URL with your collaborators. However, before they can clone and push changes to your shared project, you need to give them read and write access for the remote Git repository of your project. This can be done in your Git provider’s settings, where you can add collaborators and assign them permissions. You do not need to give them an administrator role in your SAP BTP global account or read and write access to the SAP Business Application Studio workspace. These are not related to the Git repository of your project1. References:

• 1: Sharing the Project via Git - SAP Learning

The Test step in a CI/CD job allows you to deploy your application to a Cloud Foundry environment. This is useful for testing your application in a sandbox or staging space before deploying it to a production space. You can configure the Test step to use a different Cloud Foundry organization, space, or subaccount than the one you are using for development. You can also specify the test commands and scripts to run after the deployment. The other options are not valid for the Test step in a CI/CD job. References:

• SAP Help Portal
• SAP Learning

To assign roles for users to access your deployed application, you need to use the SAP BTP Cockpit and navigate to the Security section. There you can create and manage role collections, which are groups of roles that define the permissions for accessing resources and services in SAP BTP. You can assign role collections to individual users or user groups, depending on your identity provider configuration. For example, if you have deployed an SAP Fiori elements application, you need to assign the role collection sap_business_application_studio_ui_deployer to the users who need to access the application. This role collection contains the role sap_business_application_studio_ui_deployer_role, which is based on the role template sap_business_application_studio_ui_deployer_role_template. This role template grants the user the permission to access the deployed UI application. References:

• SAP Help Portal
• 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