[2024年11月] ベストな問題集を使おうSAP Certified Associate C-WZADM-2404専門試験問題
100%の合格率を試そう！更新されたのはC-WZADM-2404試験問題 [2024]
質問 # 30
Which characteristics are applicable to Launchpad (shell) plugins, but not to UI integration cards? (Choose three.)
- A. The source code can be downloaded directly from SAP BTP cockpit.
- B. They are managed via the administration console of DWS.
- C. They are listed in the Content Manager based on the HTMLS content provider setup.
- D. The application logs can be accessed from SAP BTP cockpit.
- E. The SAP Build Work Zone Advanced extension is required in SAP Business Application Studio.
正解：A、D、E
解説：
Launchpad (shell) plugins are a way to extend the functionality and appearance of the SAP Build Work Zone header bar, sub-navigation bar, user menu, and user settings. They are different from UI integration cards, which are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. Some of the characteristics that are applicable to launchpad (shell) plugins, but not to UI integration cards, are:
The SAP Build Work Zone Advanced extension is required in SAP Business Application Studio: This extension provides a set of tools and templates to create, test, and deploy launchpad (shell) plugins to SAP Build Work Zone. It also enables the direct deployment of the launchpad (shell) plugin 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 file1.
The application logs can be accessed from SAP BTP cockpit: Since launchpad (shell) plugins are deployed as HTML5 applications to SAP BTP, their application logs can be viewed and downloaded from the SAP BTP cockpit, under the HTML5 Applications section. This can help troubleshoot any issues or errors that occur during the runtime of the launchpad (shell) plugin2.
The source code can be downloaded directly from SAP BTP cockpit: Another feature of deploying launchpad (shell) plugins as HTML5 applications to SAP BTP is that their source code can be downloaded as a ZIP file from the SAP BTP cockpit, under the HTML5 Applications section. This can help backup or restore the launchpad (shell) plugin code, or share it with other developers2.
The characteristics that are not applicable to launchpad (shell) plugins, but to UI integration cards, are:
They are managed via the administration console of DWS: UI integration cards are managed via the administration console of SAP Build Work Zone, under the UI Integration Cards section. Here, users can upload, view, edit, and delete the UI integration cards that are available for their site. Launchpad (shell) plugins are not managed via the administration console, but via the SAP Business Application Studio or the SAP BTP cockpit34.
They are listed in the Content Manager based on the HTMLS content provider setup: UI integration cards are listed in the Content Manager of SAP Build Work Zone, under the HTMLS content provider, which is a way to connect to external HTML5 applications or UI integration cards. Users can browse, search, and add the UI integration cards to their site pages using the Content Manager. Launchpad (shell) plugins are not listed in the Content Manager, as they are not considered as content, but as extensions4 .
質問 # 31
Which of the following describes how SAP Build Work Zone & SAP SuccessFactors Work Zone are available?
- A. Service on SAP Business Technology Platform (NEO)
- B. Service on SAP Business Technology Platform (Cloud Foundry)
- C. Standalone on-premise solution
- D. SAP SuccessFactors module
正解：B
解説：
SAP Build Work Zone is a service on SAP Business Technology Platform (SAP BTP) that runs on the Cloud Foundry environment. It is not available on the NEO environment, nor as a standalone on-premise solution. SAP SuccessFactors Work Zone is a product that provides HR-specific content and integration with SAP SuccessFactors HXM Suite on the SAP Build Work Zone, advanced edition solution. It is not a separate module of SAP SuccessFactors, but rather a complementary offering that enhances the user experience and productivity of HR processes. Reference: What you should know about SAP Build Work Zone, standard and advanced edition - formerly known as SAP Launchpad Service and SAP Work Zone | SAP Blogs, SAP Build Work Zone, advanced edition | SAP Help Portal, SAP SuccessFactors Work Zone | SAP Help Portal
質問 # 32
Which artifact must be deleted manually after a content package has been removed?
- A. UI integration cards
- B. SAP BTP destinations
- C. Workspace templates
- D. Workpage configuration
正解：A
質問 # 33
Which of the following schemas of an SAP Build Work Zone URL that is visible to end users is correct?
- A. https://<unique subdomain><DWS datacenter><work zone type>.ondemand.com
- B. https:/ /<subaccount subdomain><work zone type>.cfapps.<subaccount datacenter> hana.ondemand.com
- C. https://<DWS datacenter><work zone type><unique subdomain>.ondemand.com
- D. https://<subaccount datacenter><work zone type> cfapps.<subaccount subdomain>hana.ondemand.com
正解：A
解説：
The schema of an SAP Build Work Zone URL that is visible to end users is composed of the following elements:
The unique subdomain, which is a custom name chosen by the customer when creating the SAP Build Work Zone service instance.
The DWS datacenter, which is the region where the service instance is deployed, such as eu10, us10, or ap10.
The work zone type, which is either workzone for SAP Build Work Zone, standard edition, or workzoneadv for SAP Build Work Zone, advanced edition.
The suffix .ondemand.com, which is the domain name for SAP Cloud Platform applications.
Therefore, the correct schema is https://<unique subdomain><DWS datacenter><work zone type>.ondemand.com.
The other options are incorrect because they do not follow the correct order or format of the URL elements. They also confuse the subaccount subdomain and the subaccount datacenter with the unique subdomain and the DWS datacenter. The subaccount subdomain and the subaccount datacenter are related to the SAP BTP subaccount that hosts the SAP Build Work Zone service instance, not the URL that is visible to end users.
Reference:
Introducing SAP Build Work Zone, Unit 2, Lesson 1, Slide 5
SAP Build Work Zone - Implementation and Administration, Unit 2, Lesson 2, Slide 6
質問 # 34
What are some actions that external users CANNOT do? (Choose three.)
- A. Upload a custom profile picture
- B. Post in workspace forums
- C. Access My Workspace
- D. Share user homepages with other external users
- E. Create workspaces
正解：C、D、E
解説：
External users are the most restricted user type in SAP Build Work Zone, advanced edition. They are guests of your organization and are given access to only the specific private external workspaces to which they have been invited, as well as to their dedicated home pages (for external users) and their user profile1. Therefore, some actions that external users cannot do are:
Create workspaces: External users cannot create workspaces of any type. They can only join workspaces that they are invited to by internal users or other external users2.
Share user homepages with other external users: External users cannot share their user homepages with other external users. They can only view their own user homepage, which shows the workspaces they are a member of and the content they have recently accessed3.
Access My Workspace: External users cannot access My Workspace, which is a personal workspace for internal users where they can store and manage their own content. External users can only access the workspaces they are invited to and the content they are allowed to see4.
External users can do the following actions:
Post in workspace forums: External users can post in workspace forums of the workspaces they are a member of. They can also subscribe to topics, receive notifications, and mark answers as helpful or correct5.
Upload a custom profile picture: External users can upload a custom profile picture for their user profile. They can also edit their profile information, such as name, email, phone number, and bio.
Reference:
1: External Users - Overview
2: Managing External Users
3: User Home Page for External Users
4: My Workspace
5: Forum Section
: User Profile
質問 # 35
In which SAP Activate phase are the tasks of the cutover plan executed?
- A. Run
- B. Deploy
- C. Realize
- D. Explore
正解：B
解説：
The tasks of the cutover plan are executed in the Deploy phase of SAP Activate. The Deploy phase covers the implementation of the target SAP solution into a Productive (Go Live) state for use by the target business users; this is referred to as the Project Cutover1. The cutover plan describes all required tasks that must be performed before the go-live and needs to cover the following tracks: Infrastructure, System Design, Security, Data, and Training2. The cutover plan is refined and updated during or after the cutover simulation, which is also part of the Deploy phase1. The Deploy phase ends with the successful go-live of the SAP solution and the transition to the Run phase3. Reference: 1: SAP Project Manager's Guide to SAP Project Cutover 2: Cutover highlights for SAP S/4HANA New implementation 3: SAP Activate Elements and Phases
質問 # 36
Please match actions to the SCIM API user endpoints.POST /Users PATCH /Users/{id} GET /Users PUT /Users/{id}
- A. Return a list of user profiles
- B. Create a user profile
- C. Update the entire user profile
- D. Update specific fields of a user profile
正解：B
解説：
Action
Endpoint
Create a user profile
POST /Users
Update specific fields of a user profile
PATCH /Users/{id}
Update the entire user profile
PUT /Users/{id}
Return a list of user profiles
GET /Users
The {id} parameter is a unique identifier for each user profile. The POST, PATCH, and PUT methods require a JSON body that contains the user attributes and values to be created or updated. The GET method can accept query parameters to filter, sort, or paginate the user profiles. For more details, you can refer to the SCIM 2.0 specification1 or the Microsoft Entra SCIM implementation2
質問 # 37
Which of the following tasks can you accomplish using SAP Build Work Zone APis? (Choose three.)
- A. Granting access to single pages
- B. Query data
- C. Subscribe to events
- D. Notify gamification service
- E. Create new content
正解：A、B、E
解説：
SAP Build Work Zone APIs are application programmable interfaces that allow other SAP or third party solutions to integrate with SAP Build Work Zone, to either query data-based on scope, or create new content. Some of the tasks that can be accomplished using SAP Build Work Zone APIs are:
Granting access to single pages: APIs support single-use tokens for granting immediate, short-term access to single pages1.
Create new content: APIs can be used to create new content packages, HTML5 applications, extensions, or UI integration cards1.
Query data: APIs can be used to query data from SAP Build Work Zone, such as users, groups, pages, spaces, or notifications1.
The other options are incorrect because they are related to webhook subscriptions, not APIs. Webhook subscriptions are used to register for notifications of certain updates or activities within SAP Build Work Zone, such as page creation, space deletion, or user invitation1. Webhooks can also be used to notify gamification service, which is a third party service that provides gamification features for SAP Build Work Zone2.
Reference:
Explaining APIs and Webhooks, Unit 2, Lesson 3, Slides 3-6
SAP Build Work Zone Webhook Document, Section 2.1.1
質問 # 38
A user cannot access the administration console of SAP Build Work Zone.What could be a reason?
- A. Administrator permission in Digital Workspace Service is missing
- B. SAP BTP subaccount viewer role collection is missing
- C. Space manager permission on SAP BTP subaccount level is missing
- D. SAP BTP global account viewer role collection is missing
正解：A
解説：
To access the administration console of SAP Build Work Zone, you need to have the administrator permission in Digital Workspace Service. This permission is granted by the company administrator or the area administrator of the site that you want to access. Without this permission, you will not see the Administration Console option under your avatar in the User Actions menu. The other options (B, C, and D) are not related to the administration console access, but to the SAP BTP account and subaccount level permissions that are required for setting up SAP Build Work Zone. Reference:
SAP Build Work Zone, advanced edition - SAP Online Help
SAP Build Work Zone - Implementation and Administration
質問 # 39
Which of the following features can you enable as sections in a workspace? (Choose three.)
- A. Content
- B. Worl<pages
- C. Applications
- D. Messages
- E. Forums
正解：A、B、E
解説：
You can enable the following features as sections in a workspace: content, workpages, and forums. The content section allows you to add different types of content to your workspace, such as cards, widgets, applications, documents, links, and videos. The workpages section allows you to create and edit pages that display content in a flexible layout. The forums section allows you to create and participate in discussions with other workspace members. You can also subscribe to topics, receive notifications, and mark answers as helpful or correct. The applications and messages features are not available as sections in a workspace, but you can access them from other places. You can add applications to your workspace as content items or as tiles on your workpages. You can access messages from the notification center or from the SAP Mobile Start app. Reference:
Content section: [Content Section]
Workpages section: [Workpages Section]
Forums section: [Forum Section]
Applications: [Applications]
Messages: [About Notifications] and [SAP Mobile Start]
質問 # 40
Which SAP Build Work Zone administrator type can be assigned using the DWS SCIM API?
- A. Company administrator
- B. Support administrator
- C. Area administrator
- D. Page Content administrator
正解：A
解説：
The DWS SCIM API is a REST API based on the System for Cross-domain Identity Management (SCIM 2.0) specification that is used to manage users and user lists in the Digital Workplace Service (DWS) layer of SAP Build Work Zone1. The DWS SCIM API can be used to assign the company administrator role to users who are authorized to manage the entire SAP Build Work Zone tenant2. The company administrator role is required in addition to the role collection that is assigned to users on the SAP BTP subaccount level2.
The other options are incorrect because they are not assigned using the DWS SCIM API, but rather using the Site Manager UI or the Content Manager API. The support administrator role is assigned to users who can access the support tools and troubleshoot issues in SAP Build Work Zone3. The area administrator role is assigned to users who can manage a specific area within SAP Build Work Zone, such as spaces, pages, or notifications. The page content administrator role is assigned to users who can create and edit pages in SAP Build Work Zone.
Reference:
Explaining APIs and Webhooks, Unit 2, Lesson 3, Slide 5
Manage Administrators Using SCIM API, Section 2.2
About the Site Manager, Section 2.1
[About Roles and Role Assignment Restrictions], Section 2.2
[Create and Edit Pages], Section 3.1
質問 # 41
Which of the following artifacts can be included in a content package? (Choose three.)
- A. Workspace templates
- B. Workflows
- C. Launchpad (shell) plugins
- D. UI Integration Cards
- E. SAP Fiori applications
正解：A、B、D
解説：
A content package is a collection of content items that are bundled together in a ZIP file that can be easily uploaded and installed into your subaccount. According to the SAP Help Portal1, the content items that can be part of a content package are:
Cards
Workspace templates
Home pages
Workflows
Workspaces
Therefore, the correct answer is A, B, and D. UI Integration Cards, workspace templates, and workflows are all examples of content items that can be included in a content package. SAP Fiori applications and launchpad (shell) plugins are not content items that can be part of a content package. Reference: 1: Content Packages | SAP Help Portal
質問 # 42
Where are application tiles created and configured?
- A. DWS administration console
- B. Content Manager
- C. SAP BTP global account cockpit
- D. Work Zone configurator +f/j
正解：B
解説：
Application tiles are created and configured in the Content Manager, which is a tool located in the Site Manager of SAP Build Work Zone. The Content Manager includes various editors that you can use to configure apps, groups, roles, and catalogs. Once configured, the app appears as a tile in the Applications page of your site - a single page that acts as an embedded launchpad. You can also implement custom visualizations for your app tiles, such as Static App Launcher and Dynamic App Launcher. Reference:
7: Adding Apps to Your Site
8: Add an SAPUI5 App to a Workpage in SAP Build Work Zone, advanced edition
9: Implement Custom Visualization
質問 # 43
Which of the following key deliverables are part of the SAP Activate Explore phase? (Choose two.)
- A. Integration setup
- B. Data Load Preparation
- C. Cloud System Provisioning
- D. Fit-to-Standard Analysis
正解：B、D
解説：
The SAP Activate Explore phase is the phase where the project team validates the fit of the standard SAP solution to the customer's business requirements and identifies any gaps or deltas that need to be addressed1. The key deliverables of this phase are2:
Fit-to-Standard Analysis: This is a series of workshops where the project team demonstrates the predefined scenarios and processes in the SAP solution using the customer's starter system and sample data. The customer validates the fit of the standard solution to their business needs and identifies any gaps or deltas that require additional configuration, customization, or extension3.
Data Load Preparation: This is the process of preparing the data migration objects and templates, defining the data migration strategy and approach, and performing data quality checks and cleansing. The project team also executes the initial data load to the quality system and validates the results4.
The other options are not part of the SAP Activate Explore phase, but rather of the following phases:
Integration setup: This is part of the SAP Activate Realize phase, where the project team configures and tests the integration scenarios between the SAP solution and other systems, such as legacy systems, third-party applications, or cloud services5.
Cloud System Provisioning: This is part of the SAP Activate Prepare phase, where the project team requests and receives the access to the SAP cloud systems, such as the starter system, the quality system, and the production system6.
質問 # 44
When working with home pages, which of the following aspects need to be considered? (Choose two.)
- A. Company area home pages are always shown to all users.
- B. The home page editor has different layout options compared to workspaces.
- C. Home pages have a dedicated content area.
- D. External home pages can only be configured in the external user Company Admin Area.
正解：B、C
解説：
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.
Reference:
Home Pages
Adding Content to Workpages
External Users
質問 # 45
Which feed widget setting is used on the home page level to show all public feed updates?
- A. Company
- B. Global
- C. Public
- D. Home
正解：B
解説：
The feed widget setting that is used on the home page level to show all public feed updates is Global. The feed widget is a type of widget that embeds a feed in an external web page. The feed widget builder allows users to create and customize feed widgets using various settings, such as the feed source, the feed type, the feed layout, and the feed filter. The feed source setting determines which feed is displayed in the widget. There are four options for the feed source setting: Public, Global, Home, and Company. The Public option displays the public feed of the site, which includes all public updates from all workspaces and members. The Global option displays the global feed of the site, which includes all public and private updates from all workspaces and members that the user has access to. The Home option displays the home feed of the user, which includes all updates that are relevant to the user, such as updates from their workspaces, followed members, and @mentions. The Company option displays the company feed of the user, which includes all updates from the user's company, such as updates from their colleagues, managers, and subordinates. The feed widget setting that is used on the home page level to show all public feed updates is Global, because it shows all the updates that the user can see on the site, regardless of their workspace or member affiliation. The other options are either too restrictive (Home and Company) or too broad (Public) for the home page level. Reference:
Widget Builders
About Widgets
質問 # 46
What is the most-used method to show business data on SAP Build Work Zone workpages?
- A. Launchpad Plugins
- B. Chatbots
- C. UI Integration Cards
- D. API and Webhooks
正解：C
解説：
UI integration cards are the most-used method to show business data on SAP Build Work Zone workpages because they allow you to display application content from different sources side by side without the user having to switch screens. They contain a certain set of information from an app or page that's presented to users in a specific context. You can use cards to group information, link to more details, present a summary, and much more. As a result, your users get all the information they need on a single screen. UI integration cards can also interact with each other on the same workpage, making them more dynamic and responsive. Reference: UI Integration Cards | SAP Help Portal, Direct Deployment of UI Integration Cards to SAP Work Zone | SAP Blogs
質問 # 47
Which SAP Build Work Zone administrator types require an assignment of a role collection? (Choose three.)
- A. Support administrator
- B. Company administrator
- C. Workspace administrator
- D. Area administrator
- E. Sub-Workspace administrator
正解：A、B、C
解説：
SAP Build Work Zone administrator types are divided into three levels: company, workspace, and area. Each level has a corresponding role collection that needs to be assigned to the users who perform administrative tasks at that level. The company administrator role collection enables users to manage the overall SAP Build Work Zone service instance, such as creating workspaces, assigning workspace administrators, and configuring global settings. The support administrator role collection enables users to access the support portal and perform tasks such as viewing logs, monitoring performance, and managing incidents. The workspace administrator role collection enables users to manage a specific workspace, such as creating areas, assigning area administrators, and configuring workspace settings. The sub-workspace administrator and area administrator types do not require a role collection assignment, as they are created and managed within the SAP Build Work Zone content manager by the workspace administrator or the area administrator respectively. Reference:
SAP Build Work Zone, advanced edition - SAP Online Help
Explaining the Provisioning of Users and Roles in SAP Build Work Zone
質問 # 48
Which of the following are scenarios that could be implemented with extensions for SAP Build Work Zone, advanced edition? (Choose three.)
- A. Show a list of flights or hotels booked by the user in the corporate travel system
- B. Ensure single-sign-on experience for all users
- C. Show a list of incidents reported by a user from an on-premise or cloud system
- D. Change the system logo and color scheme
- E. Create a new link to corporate policies in the user menu
正解：A、C、D
解説：
Extensions for SAP Build Work Zone, advanced edition are custom applications that can be developed and deployed to enhance the user experience and functionality of SAP Build Work Zone, advanced edition. Extensions can be used to integrate data and content from various sources, such as SAP or third-party systems, into SAP Build Work Zone, advanced edition. Extensions can also be used to customize the look and feel of SAP Build Work Zone, advanced edition, such as changing the logo, color scheme, or layout. Extensions can be developed using SAP Business Application Studio or any other development tool that supports the Cloud Foundry environment12.
The scenarios that could be implemented with extensions for SAP Build Work Zone, advanced edition are:
Show a list of flights or hotels booked by the user in the corporate travel system (B): This scenario requires integrating data from an external system (the corporate travel system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.
Change the system logo and color scheme (D): This scenario requires customizing the appearance of SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to modify the system settings, such as the logo, color scheme, or theme5.
Show a list of incidents reported by a user from an on-premise or cloud system (E): This scenario requires integrating data from another SAP or third-party system (the incident management system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.
The scenarios that could not be implemented with extensions for SAP Build Work Zone, advanced edition are:
Ensure single-sign-on experience for all users (A): This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already supports single-sign-on (SSO) for all users. SSO can be configured by the administrator using the SAP Cloud Platform Identity Authentication service.
Create a new link to corporate policies in the user menu : This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already allows adding custom links to the user menu. This can be done by the administrator using the SAP Build Work Zone, advanced edition UI.
質問 # 49
In My Inbox, you can access content from which of the following components?
- A. Notifications from other SAP solutions
- B. Workflows from SAP BTP Workflow Management
- C. Notifications from SAP SuccessFactors
- D. Workflows from SAP Build Work Zone
正解：A、B、D
解説：
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. Reference:
Using My Inbox
Configure My Inbox App
Exploring the Information Architecture
質問 # 50
To use SAP Build Work Zone OData APis or webhooks, you must connect to which of the following?
- A. SAP API Management
- B. SAP BTP subaccount
- C. Content Manager
- D. Digital Workplace Service (DWS)
正解：D
解説：
To use SAP Build Work Zone OData APIs or webhooks, you must connect to the Digital Workplace Service (DWS) component of the SAP Build Work Zone solution architecture. The DWS is responsible for providing the APIs and webhooks that enable integration with other SAP or third party solutions. The DWS also handles the user authorization and authentication using OAuth or SAML workflows. The other options are not correct because they are not related to the SAP Build Work Zone APIs and webhooks. Content Manager is a tool for managing content in SAP Build Work Zone, SAP BTP subaccount is a logical unit for managing applications and services on SAP Business Technology Platform, and SAP API Management is a service for managing, securing, and analyzing APIs. Reference:
Explaining APIs and Webhooks
Using Push Notifications for Webhooks
質問 # 51
What is a characteristic of administrative areas?
- A. The company area membership is optional
- B. The company area can be created optionally.
- C. The company area cannot be edited.
- D. The company area is created by default.
正解：D
解説：
An administrative area is a designated space for subject matter experts to manage content and interact within their lines of business. Company administrators assign area administrators to administrative areas. Area administrators have a subset of company administrator capabilities to perform area-related tasks. The company area is created by default and it is the top level of the internal structure of the site. Information on the company level is visible to all users in the company. There can only be one company level. If you want to add multiple subsidiaries or business areas, you can create different administrative areas for them. Reference:
Administrative Areas
Area & Workspace Configuration
質問 # 52
What can you use to assign role collections to users? (Choose three.)
- A. Attribute mapping for the connected Identity Provider
- B. Digital Workplace Service SCIM API
- C. Admin UI of the SAP BTP subaccount cockpit
- D. SAP Build Work Zone Content Manager
- E. Authorization & Trust Management Service API
正解：A、B、C
解説：
This is a REST API based on the System for Cross-domain Identity Management (SCIM 2.0) specification that allows you to assign roles to users directly inside SAP Build Work Zone1.
Admin UI of the SAP BTP subaccount cockpit: This is a graphical user interface that allows you to assign role collections to users on the SAP BTP subaccount level234.
Attribute mapping for the connected Identity Provider: This is a configuration option that allows you to automatically create shadow users and map role collections based on the Groups assertion attribute from the connected Identity Provider1.
質問 # 53
......
C-WZADM-2404試験問題を今すぐ試そう！最新の[2024年最新] 正解回答付き：https://www.passtest.jp/SAP/C-WZADM-2404-shiken.html
合格させるC-WZADM-2404試験にはリアル問題解答：https://drive.google.com/open?id=1tQbZzmcWFv-gYPUkBn0wgPb6Uzr5d2z9