Go to C_WZADM_01 Questions – Try C_WZADM_01 dumps pdf [Q29-Q47]

Explanation
UI Integration Cards are reusable components that display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. They can be deployed to SAP Build Work Zone using one of the following methods:
* Admin Console in SAP Build Work Zone: This method allows users to manually upload a ZIP file that contains the UI card definition and resources to the Admin Console UI Integration Cards section, using the Upload Card button. Users can also view, edit, and delete the existing UI cards in the Admin Console1.
* SAP Business Application Studio: This method allows users to directly deploy the UI card from SAP Business Application Studio to SAP Build Work Zone, using the UI Integration Card: Deploy to SAP Build Work Zone, advanced edition option in the context menu of the manifest.json file. This method requires the subscription to SAP Business Application Studio to exist on the same subaccount as the subscription to SAP Build Work Zone, and a token-exchange destination to be configured. Users can also package the UI card into a ZIP file and download it for manual upload, using the UI Integration Card: Package option2.
The methods that are not used to deploy UI Integration Cards to SAP Build Work Zone are:
* Command Line Interface (CLI): This method is not supported by SAP Build Work Zone, as there is no CLI tool available for UI Integration Cards development or deployment.
* Content Manager: This method is used to manage the unstructured content in SAP Build Work Zone, such as blogs, multimedia, surveys, polls, wiki pages, events, knowledge base articles,tasks, and feeds. It is not used to deploy UI Integration Cards, which are considered as structured content3.

Guided experience refers to a user interface design technique that guides users through a predefined workflow or process. Using guided experience, users are presented with step-by-step instructions, prompts, and visual cues to help them complete a specific task or achieve a particular goal.
Based on this definition, option B – perform tasks through a multistep process that can span multiple systems – is the most accurate choice. Guided experience is often used to facilitate complex tasks that involve multiple steps and systems, such as filling out a form, setting up an account, or completing a purchase.
Option A – create workspaces using pre-built templates – is also a possible use of guided experience. Guided experience can help users navigate through the process of creating a new workspace by providing them with pre-built templates and guiding them through the customization process.
Option C – modify the workpage content structure – is not typically associated with guided experience. While guided experience can help users modify the content of a page, it is more commonly used to guide users through a predefined workflow or process, rather than allowing them to modify the structure of the page itself.

The actions that external users CANNOT do are:
1. Create workspaces
2. Share user homepages with other external users
3. Access My Workspace
External users are usually restricted to a specific workspace or set of workspaces and do not have the same level of access and permissions as internal users. They cannot create workspaces or share user homepages with other external users, as these actions require elevated permissions. Additionally, they cannot access My Workspace, which is typically reserved for internal users. However, external users may be able to post in workspace forums and upload a custom profile picture, depending on the specific permissions granted to them by the workspace owner or administrator.

Explanation
To implement SAP Build Work Zone, advanced edition in a multi-tier landscape, you need to create subscriptions in separate SAP BTP subaccounts. This is because SAP Build Work Zone, advanced edition is a subscription-based service that requires a dedicated subaccount for each tenant. You cannot create multiple subscriptions or service instances in the same subaccount, nor can you create multiple sites within a single subscription. Each subscription represents a separate site with its own content, configuration, and users. By creating subscriptions in separate subaccounts, you can align your SAP Build Work Zone landscape with your core business system landscape and enable content transport across different tiers. References:
* Explaining the Planning Landscape for SAP Build Work Zone
* Getting Started With SAP Build Work Zone

Explanation
In My Inbox, you can access content from the following components:
* Workflows from SAP Build Work Zone: You can process tasks that are created by workflows that you design and run on SAP Build Work Zone. For more information, see Using My Inbox.
* Workflows from SAP BTP Workflow Management: You can process tasks that are created by workflows that you design and run on SAP Business Technology Platform Workflow Management. For more information, see Configure My Inbox App.
* Notifications from other SAP solutions: You can receive notifications from other SAP solutions that are integrated with SAP Build Work Zone, such as SAP SuccessFactors, SAP S/4HANA, SAP Ariba, and SAP Fieldglass. For more information, see Exploring the Information Architecture. The option B is not correct because notifications from SAP SuccessFactors are not accessed directly in My Inbox, but rather through the integration with SAP Build Work Zone. References:
* Using My Inbox
* Configure My Inbox App
* Exploring the Information Architecture

1. They can call multiple backend systems.
2. Destinations must be maintained at the SAP BTP subaccount level.
UI integration cards can call multiple backend systems, which makes them versatile in integrating various types of data sources into the UI. Additionally, destinations must be maintained at the SAP BTP subaccount level, which ensures that the necessary connectivity is established between the UI integration card and the backend systems.

Based on the given options, the step in which role collections are created is not clear. The creation of role collections may vary depending on the specific product and setup process being referred to.
Could you please provide more context or details about the product and setup process you are referring to? That would enable me to give a more accurate answer.

The Web Content Card in SAP Build Work Zone workpages uses the <iframe> HTML tag to embed internal and external web pages. The <iframe> tag allows you to embed a web page within another web page. This is useful for displaying external content, such as a news feed or weather report, or for displaying internal content from your own website. The <iframe> tag has several attributes that allow you to control the appearance and behavior of the embedded content, such as width, height, scrolling, and border.

Explanation
UI integration cards are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. They can support operations on the UI, such as choosing the card header or a button, and they can call multiple backend systems using destinations.
Destinations are a way to connect to external services or applications using a simple name. They must be maintained at the SAP BTP subaccount level and have the HTMLS.ForwardAuth Token property set to true.
This property enables the SAP Build Work Zone to forward the authentication token to the destination service.
UI integration cards cannot only consume business data from SAP systems, but also from non-SAP systems, as long as they are accessible via destinations.
For more information about UI integration cards, you can refer to the following resources:
* UI Integration Cards | SAP Help Portal1
* Direct Deployment of UI Integration Cards to SAP Work Zone | SAP Blogs2
* Developing UI Integration Cards | SAP Help Portal3
* SAP Build Work Zone, advanced edition – SAP Online Help4

Explanation
Shadow users are users that are created in the SAP BTP subaccount to map the users from the connected identity provider. Shadow users are required for users to access SAP Build Work Zone. The following methods can be used to create shadow users:
* Automatic creation upon login via connected identity provider: This is the recommended and default method for creating shadow users. When a user logs in to SAP Build Work Zone for the first time using an identity provider such as SAP Cloud Identity Services, a shadow user is automatically created and assigned to the role collections that are mapped to the groups attribute in the identity provider1.
* Admin UI on the SAP BTP subaccount cockpit: This is a manual method for creating shadow users. An administrator can use the SAP BTP subaccount cockpit to create and manage shadow users and assign them to role collections2.
* Authorization & Trust Management Service API: This is a programmatic method for creating shadow users. An administrator can use the Authorization & Trust Management Service API to create, read, update, and delete shadow users and assign them to role collections3.
The following methods cannot be used to create shadow users:
* Import from SAP SuccessFactors Employee Central: This method can be used to import users from SAP SuccessFactors Employee Central to SAP Cloud Identity Services, but not to create shadow users in the SAP BTP subaccount.
* CSV file upload in the SAP BTP subaccount cockpit: This method can be used to upload users and assign them to role collections in the SAP BTP subaccount, but not to create shadow users. Shadow users are created only when the users log in via the connected identity provider. References:
* 1: Explaining the Authentication Flow of SAP Build Work Zone
* 2: Assign SAP Build Work Zone Roles to Users
* 3: Authorization & Trust Management Service API
* : Importing Users from SAP SuccessFactors Employee Central
* : Uploading Users and Assigning Them to Role Collections

Without more context or information about the specific application or platform in question, it is difficult to give a definitive answer. However, based on the options provided, application tiles could be created and configured in any of these places, depending on the specific platform and its features:
1. Work Zone configurator +f/j: This option suggests that the application tiles may be related to SAP Work Zone, a platform for creating and customizing digital workspaces. The Work Zone configurator could be used to create and configure application tiles within a Work Zone workspace.
2. Content Manager: This option is less specific, as “Content Manager” could refer to a variety of different platforms or tools. However, it is possible that an application’s tiles could be managed or configured through a content management system, particularly if the application involves displaying or managing various types of content.
3. DWS administration console: Again, without more context it is difficult to say for certain, but this option suggests that the application tiles may be related to SAP Document Management System (DMS), which includes an administration console for managing DMS objects.
4. SAP BTP global account cockpit: This option suggests that the application tiles may be related to SAP Business Technology Platform (BTP), a cloud platform for building and running applications. The global account cockpit is a central management console for managing BTP resources, and could potentially be used to create and configure application tiles for BTP applications.

Explanation
Home pages are the landing pages that users see when they access SAP Build Work Zone. They can display information that is relevant to the company, an area, or a workspace. There are some aspects that need to be considered when working with home pages, such as:
* Home pages have a dedicated content area that can be customized using the page builder. The content area is where you can add rows, columns, widgets, cards, and other elements to create a layout for your home page. The content area is different from the feed area, which shows the latest updates and notifications from the company, area, or workspace1.
* The home page editor has different layout options compared to workspaces. The home page editor allows you to create a persistent navigation bar with links to other pages or external URLs. You can also add a header image and a title to your home page. The workspace editor does not have these options, but it allows you to add tabs to organize your content into different pages2.
Some aspects that are not true about home pages are:
* External home pages can only be configured in the external user Company Admin Area. This is not true, because external home pages can also be configured in the external user Area Admin Area. External home pages are the home pages that are shown to external users, who are users that do not belong to your company but have access to some of your content. You can create external home pages for the company level and for each area level. To do so, you need to switch to the external user Company Admin Area or the external user Area Admin Area, which are separate from the internal user admin areas3.
* Company area home pages are always shown to all users. This is not true, because company area home pages are only shown to the users who belong to that specific area. Company area home pages are the home pages that are designed for a specific area or department within the company. They display information that is relevant to that area and also include the area feed. Content is shared by everyone in the specific area. To create a company area home page, you need to be an administrator that is assigned to that area1.
References:
* Home Pages
* Adding Content to Workpages
* External Users

Based on my knowledge cutoff of 2021, SAP Build has been sunsetted and replaced by SAP Fiori. However, assuming that extensions for SAP Build Work Zone, advanced edition are still available, the three scenarios that could be implemented with these extensions are:
1. Ensure single-sign-on experience for all users
2. Show a list of flights or hotels booked by the user in the corporate travel system
3. Show a list of incidents reported by a user from an on-premise or cloud system