Correct Answer:

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to use the correct SAP app to verify that the bank master data migrated in the previous task was created successfully in the target system.
The correct verification app is:
Manage Banks - Master Data
SAP's documentation for bank maintenance assigns this app to the bank master data role and uses it for maintaining and checking bank records, which matches the verification step after migration.
Business Scenario Explanation
In the previous migration tasks, you:
created the migration project,
selected the Bank migration object,
prepared and uploaded the bank data,
validated and transferred it to staging tables,
completed mapping tasks,
migrated the two bank records.
However, a migration is not considered complete until the data is verified in the target application used for ongoing business maintenance.
For the Bank migration object, that target verification app is:
Manage Banks - Master Data
This app allows you to search for the migrated banks and confirm that the data now exists in SAP S/4HANA Cloud Public Edition.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact bank values that were migrated.
Verification must be done in the correct app, not only in the migration cockpit.
The expected bank records are the two banks from the previous task.
Correct Verification App
Purpose
App
Verify migrated bank master data
Manage Banks - Master Data
SAP documents that bank master maintenance is handled through the bank master data application and the associated bank maintenance role/catalog, which is why this is the correct end-user verification app after bank migration.
Data to Verify
You should verify the two migrated banks:
Bank 1
Bank Country/Region = US
Bank Key = A######
Bank Name = Bank of A######
Bank 2
Bank Country/Region = US
Bank Key = Z######
Bank Name = Bank of Z######
Example
If your suffix is 000013, verify:
US / A000013 / Bank of A000013
US / Z000013 / Bank of Z000013
Detailed Step-by-Step Procedure
Step 1: Return to the SAP Fiori launchpad
After finishing the migration:
Go back to the SAP S/4HANA Cloud homepage.
Explanation:
The verification must be performed in the target business app, not only from the migration results screen.
Step 2: Open the app "Manage Banks - Master Data"
From the launchpad search:
Search for:
Manage Banks - Master Data
Open the app.
Explanation:
This is the correct app for checking whether the migrated bank master records now exist in the target system.
Step 3: Search for the first migrated bank
In Manage Banks - Master Data:
In Bank Country/Region, enter:
US
In Bank Key, enter:
A######
Click Go
Example
If your suffix is 000013, search for:
Bank Country/Region = US
Bank Key = A000013
Explanation:
This checks whether the first migrated bank was created successfully.
Step 4: Verify the first bank details
Confirm that the search result shows the correct bank record:
Bank Country/Region = US
Bank Key = A######
Bank Name = Bank of A######
You can also verify address data if visible, such as:
Street = West Chester Pike
City = Newtown Square
Explanation:
This confirms that the first bank master record exists in the target system after migration.
Step 5: Search for the second migrated bank
Clear or update the search criteria and enter:
Bank Country/Region = US
Bank Key = Z######
Click Go
Example
If your suffix is 000013, search for:
Bank Country/Region = US
Bank Key = Z000013
Explanation:
This checks whether the second migrated bank was created successfully.
Step 6: Verify the second bank details
Confirm that the second search result shows:
Bank Country/Region = US
Bank Key = Z######
Bank Name = Bank of Z######
You can also verify address data if visible, such as:
Street = Lenox Road
City = Atlanta
Explanation:
This confirms that the second bank master record exists in the target system after migration.
Step 7: Confirm successful verification
If both banks are visible in Manage Banks - Master Data, the migration verification is successful.
Explanation:
This is the final proof that the migration did not only complete technically in the cockpit, but also posted the expected business data into the target application.
Expected Result
After this task is completed successfully:
the app Manage Banks - Master Data is used for verification,
Bank 1 is visible:
US / A###### / Bank of A######
Bank 2 is visible:
US / Z###### / Bank of Z######
the migrated bank data is confirmed as successfully created in the target system.

Correct Answer:

See Explanation below for all solution
Explanation:
Task 8: Create a New Business Role (Not from a Template)
Objective
The purpose of this task is to create a new custom business role for all employees in the organization. This role is intended to become the base role that will later be connected to the required business catalogs, launchpad space, and page so that employees can easily access the relevant apps.
This task explicitly says:
create a new business role
not from a template
use the exact values provided in the task
Business Scenario Explanation
You are building a role for all employees in the organization.
Unlike the earlier project-manager role, this one is not derived from a standard SAP template.
The purpose of this role is to provide a shared employee-level launchpad structure.
Later, the role will be used to:
assign business catalogs,
create a launchpad space,
create a launchpad page,
place apps on the page for employee self-service access.
In this step, the focus is only on creating the new business role with the correct identification and access category settings.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the values exactly as shown.
Do not create this role from a template.
The access categories must be set exactly as required:
Unrestricted for all categories
Save the role at the end.
Required Values
Use the following values exactly as shown in the task screenshot

Step 1: Open the app "Maintain Business Roles"
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Use the app search.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This app is used to create, maintain, copy, derive, and restrict business roles.
Since this task requires creating a brand new custom role, this is the correct place to start.
Step 2: Start creating a new business role
Inside Maintain Business Roles:
Click New
Explanation:
This task explicitly says to create a role not from a template.
So you must use New, not:
Create From Template
Create Derived Business Role
Copy
Using New creates a completely customer-defined business role.
Step 3: Enter the business role ID
In the new business role creation screen:
In Business Role ID, enter:
Z_EMPLOYEES_ALL_######
Example
For suffix 000013:
Z_EMPLOYEES_ALL_000013
Explanation:
This is the technical identifier of the new business role.
It must match the task exactly for validation to succeed.
Step 4: Enter the business role description
In Business Role Description, enter:
All Employee Role ######
Example
For suffix 000013:
All Employee Role 000013
Explanation:
This is the readable description shown in SAP and should exactly match the exercise requirement.
Step 5: Set access categories
In the Access Categories section, set all categories to:
Write, Read, Value Help = Unrestricted
Read, Value Help = Unrestricted
Value Help = Unrestricted
Explanation:
The task explicitly says:
Access Categories: Unrestricted for all categories
So all three category dropdowns must be left or set to Unrestricted.
This means:
the role is not restricted by country, company code, or other field-level limitation in this step, this role is intended to be broadly reusable for all employees.
Step 6: Review the role before saving
Before saving, verify:
Business Role ID is correct
Business Role Description is correct
all 3 access category values are Unrestricted
Explanation:
This avoids common mistakes such as:
wrong suffix,
extra spaces,
restricted instead of unrestricted values,
creating from template accidentally.
Step 7: Save the role
Click:
Save
Explanation:
This finalizes the new business role.
Without saving, the role remains only in draft and is not actually created.
Step 8: Verify the role after save
After saving, confirm that the role is displayed with:
Business Role ID = Z_EMPLOYEES_ALL_######
Business Role Description = All Employee Role ######
Write Access / Read Access / Value Help Access = Unrestricted
Explanation:
This is the confirmation that the role was created successfully and matches the task requirement.
Expected Result
After the task is completed successfully:
a new custom business role exists,
it was created not from a template,
the role ID and description match the required values,
all access categories are Unrestricted,
the role is saved and available for the next steps.