C_ADBTP Exam Questions: Free SAP System Tasks [2026]

Step-by-Step Execution:

1. From the SAP Automation Pilot sidebar navigation, choose Terms and Conditions.
2. Switch on the toggle to enable the Content Generation Assistant, check the consent box, and choose Accept.
3. Navigate to the Commands section and click the Generate button.
4. Choose a catalog to store the command, add a command name, and provide a text prompt describing your required ops automation flow.
5. Click Generate so SAP Automation Pilot builds the command with the necessary input keys and executors.
6. Navigate to the Inputs section to manually define the required inputs and values (e.g., app URL, Jira credentials).
7. To capture more details, navigate to Command Executors, click Generate, provide a new prompt to add technical insights as comments, and review the updated executor.
8. Trigger the command and inspect the outcomes on the Execution Overview page.

Example Values:

• Initial Prompt: "Sends an HTTP request to appUrl. If response body contains DOWN, restart the Cloud Foundry app and create a Jira issue in project CLMTEST of type Bug using input keys prefixed with jira."
• Enhancement Prompt: "If the response body contains DOWN, add an initial comment to the Jira issue with information about the Cloud Foundry application name, app region, and app subaccount."

Expected Result: A fully functional, no-code operational workflow is successfully generated. Upon execution, the automation checks the application state, automatically captures in-depth technical information, and accurately opens a targeted Jira ticket to expedite root cause analysis.

Quick Mistakes:

• Assuming GenAI automatically provisions input values; users must manually define the required inputs and their values before executing the command.
• Attempting to enable the Content Generation Assistant without having the required GenAI role assigned in the subaccount.

Exam Insight: What concept is tested: Leveraging the SAP Automation Pilot GenAI assistant to design, enrich, and execute automated operations flows. Why it matters for exam: Knowing how to use low-code/no-code GenAI tools to streamline DevSecOps and ITSM integrations (like Jira) is a modern focus for SAP BTP exams, testing an administrator's ability to efficiently reduce manual operational effort.

Step-by-Step Execution:

• Open the SAP BTP cockpit and navigate to your Subaccount.
• Choose Security -> Users in the navigation pane.
• Choose the Create button to open the user data dialog box.
• Enter the user's e-mail address in the User Name and E-Mail fields.
• Choose the appropriate custom identity provider from the Identity Provider dropdown list.
• Choose Create to finalize adding the user.

Example Values: E-Mail / User Name: dev.newhire@rotatingbanana.com, Identity Provider: Custom IAS Tenant.

Expected Result: The new user is securely added, visible in the Subaccount's Users list, and is ready to be assigned predefined role collections such as Subaccount Administrator or Subaccount Viewer.

Quick Mistakes:

• Entering a user ID instead of an e-mail address when using the default SAP ID service.
• Selecting the wrong identity provider, such as leaving it as the default SAP ID service instead of the corporate custom IAS tenant.

Exam Insight: This tests the understanding of SAP BTP's user management and identity provider assignment at the subaccount level, which is a foundational administrative concept necessary for establishing secure platform access in the certification exam.

Step-by-Step Execution:

1. Choose Audits from the subaccount menu in the Cloud Connector Administration UI.
2. Under Settings, edit the audit record parameters.
3. Change the Subaccount Audit Level from Off to either Security or All.
4. Change the Cross-Subaccount Audit Level from Off to either Security or All.
5. Set the Automatic Cleanup value to After 90 Days.
6. Save the settings to begin capturing audit data in the log/audit/ directory.

Example Values:

1. Subaccount Audit Level: All
2. Automatic Cleanup: After 90 Days

Expected Result: Audit log files are generated, digitally signed to ensure integrity, and old logs are automatically purged after 90 days.

Quick Mistakes:

1. Leaving the Subaccount Audit Level on "Off", resulting in no captured log data.
2. Forgetting to regularly copy the audit log files to an external persistent storage according to local regulations before the automatic cleanup deletes them.

Exam Insight:

• Evaluates understanding of Cloud Connector security operations, specifically testing the location of log files (log/audit/), retention policies, and the fact that logs are digitally signed by the Cloud Connector for integrity.

Resolution (Fix): Inspect the Terraform state of your configuration to identify missing tracking data. You will need to import the existing SAP BTP subaccount into your Terraform state or align your code to match the current remote state before applying new changes.

Prevention Tip: Regularly inspect the Terraform state and always run a plan command before applying to see what resources Terraform intends to create, modify, or destroy.

Resolution (Step-by-Step Fix):

1. Go to the Transformations tab and open the JSON Editor.
2. Locate the condition logic and correct the regex boundary syntax to include =~ and the starting/ending / symbols.
3. Example fix: "condition": "$.emails.value =~ /.*@example.com/".

Prevention Tip: Utilize the Graphical Editor instead of the JSON Editor for standard mappings, as it handles the syntax generation (like dot notation and string quotes) automatically.