[2025年更新]SailPoint-Certified-IdentityNow-EngineerはSailPoint Certificationリアルな無料試験練習テスト
無料SailPoint Certification SailPoint-Certified-IdentityNow-Engineer試験問題を提供します
質問 # 23
Is the following true about custom connectors in IdentityNow?
Solution: Custom connector are imported the identityNow UI.
- A. No
- B. Yes
正解：B
解説：
Yes, custom connectors are imported into IdentityNow via the UI. After development and testing, the custom connector configuration is uploaded to the platform through the IdentityNow interface. This allows administrators to define how the connector interacts with external systems and specify settings like account aggregation, correlation, and provisioning.
Key Reference from SailPoint Documentation:
Connector Import Process: Custom connectors are uploaded into IdentityNow through the UI, where they can then be configured and used to connect to external systems.
質問 # 24
An IdentityNow engineer has the following problem:
An identity is listed under Identities with Errors.
Is this one of the steps that should be taken to troubleshoot the issue?
Solution: Check for missing lastname, email, or uid attributes.
- A. No
- B. Yes
正解：B
解説：
Yes, checking for missing critical attributes like lastname, email, or uid is a valid step when troubleshooting an identity listed under "Identities with Errors" in SailPoint IdentityNow. These attributes are often required for proper identity processing, synchronization, and provisioning. If any of these attributes are missing or incorrectly configured, it could result in errors, preventing the identity from being fully processed by the system.
Key Reference from SailPoint Documentation:
Identity Attributes and Error Handling: SailPoint IdentityNow requires certain core identity attributes (such as lastname, email, uid) to be present and correctly populated. Missing or invalid values for these attributes can lead to errors and prevent identity synchronization or provisioning.
質問 # 25
A customer wants to configure a virtual appliance (VA) to use a static IP address. Does this file on the VA need to be modified to perform the configuration?
Solution: /home/sailpoint/proxy.yaml
- A. Yes
- B. No
正解：B
解説：
The /home/sailpoint/proxy.yaml file is used for proxy settings, not for configuring the Virtual Appliance to use a static IP address. This file is typically modified to configure outbound proxy settings for the VA if it needs to route traffic through a proxy server. Static IP address configuration is handled elsewhere, at the operating system or network configuration level.
Reference:
SailPoint IdentityNow Virtual Appliance Proxy Configuration Documentation.
SailPoint IdentityNow Network Settings Documentation.
質問 # 26
Does this correctly describe Manager Correlation?
Solution: an approval process by which identifies assigned as manager must periodically review and approve all access assigned to their employees.
- A. Yes
- B. No
正解：B
解説：
No, this statement describes Manager Certification rather than Manager Correlation. Manager Certification refers to an approval process in which managers are required to periodically review and approve the access rights of their direct reports. This is a governance feature used to ensure that employees only have the access they need, and it helps managers validate their team's access periodically. Manager Correlation, on the other hand, is about linking identities to their managers based on attributes.
Key Reference from SailPoint Documentation:
Manager Certification vs. Manager Correlation: While Manager Certification involves periodic review and approval of access by managers, Manager Correlation is strictly about linking identities to their respective managers based on defined attributes.
質問 # 27
A customer wants to configure a virtual appliance (VA) to use a static IP address. Does this file on the VA need to be modified to perform the configuration?
Solution: /home/sailpoint/config.yaml
- A. Yes
- B. No
正解：B
解説：
The /home/sailpoint/config.yaml file is not used to configure the Virtual Appliance (VA) to use a static IP address. This file is generally used for other configuration purposes related to the SailPoint IdentityNow application settings, not for network configurations like setting static IP addresses.
Network configurations are handled at the system or network service level within the VA's Linux environment.
Reference:
SailPoint IdentityNow Virtual Appliance Configuration Guide.
SailPoint IdentityNow Networking Configuration Documentation.
質問 # 28
Is this statement accurate regarding SailPoint's multi-tenant processing environment?
Solution: Updates are rolled out on a continuous basis, which allows for rapid development and deployment of new features, security updates, and bug fixes.
- A. No
- B. Yes
正解：B
解説：
Yes, SailPoint follows a continuous delivery and rolling update model for IdentityNow, which allows for the rapid development and deployment of new features, security updates, and bug fixes. Updates are rolled out automatically to tenants as part of this process, ensuring that customers always have the latest version of the platform. This continuous approach minimizes downtime and allows SailPoint to address security vulnerabilities and improve functionality in a timely manner.
Reference:
SailPoint IdentityNow Continuous Delivery and Deployment Documentation.
SailPoint IdentityNow Release Management and Update Policy Guide.
質問 # 29
The customer has a system that matches the following description. Is this a suitable connector type to use?
The system is a modern, cloud-based, web application that uses a MySQL database backend provided by the cloud platform. The database is only accessible from the web application. The web application exposes a fully compliant SCIM 2.0 interface with OAuth 2.0 client credentials.
Solution: Generic Cloud Connector
- A. Yes
- B. No
正解：B
解説：
No, the Generic Cloud Connector is not the most suitable connector type for this use case. The system described is a modern, cloud-based web application that exposes a SCIM 2.0 interface with OAuth 2.0 client credentials for authentication. The Generic Cloud Connector is typically used for systems that do not have specialized connectors but can integrate via general APIs or REST endpoints. Since the application supports SCIM 2.0, which is a standardized protocol for managing identities, the SCIM 2.0 Connector would be the more appropriate choice, as it is specifically designed for this type of integration.
Reference:
SailPoint IdentityNow SCIM 2.0 Connector Guide.
SailPoint IdentityNow Connector Overview Documentation.
質問 # 30
The customer has a system that matches the following description. Is this a suitable connector type to use?
The system is a modern, cloud-based, web application that uses a MySQL database backend provided by the cloud platform. The database is only accessible from the web application. The web application exposes a fully compliant SCIM 2.0 interface with OAuth 2.0 client credentials.
Solution: OpenLDAP Connector
- A. Yes
- B. No
正解：B
解説：
No, the OpenLDAP Connector is not suitable for this use case. OpenLDAP is designed for integrating with LDAP-based directories, and the system described is a cloud-based web application that uses a SCIM 2.0 interface with OAuth 2.0 for authentication. Since the system supports SCIM, the correct connector would be the SCIM 2.0 Connector, which is tailored for cloud-based systems with SCIM interfaces.
Reference:
SailPoint IdentityNow OpenLDAP Connector Guide.
SailPoint IdentityNow SCIM 2.0 Connector Documentation.
質問 # 31
Is the following true about the web-services connector in IdentityNow?
Solution: The connector supports SAML authentication.
- A. Yes
- B. No
正解：B
解説：
The Web Services connector in SailPoint IdentityNow does not support SAML authentication. SAML is primarily used for Single Sign-On (SSO) authentication for web applications, whereas the Web Services connector in IdentityNow typically supports Basic Authentication, OAuth, or custom header- based authentication for API-based integrations. SAML authentication is generally used for federated identity management rather than for API-based interactions.
Reference:
SailPoint IdentityNow Web Services Connector Configuration Guide.
SailPoint IdentityNow Authentication Methods for Connectors.
質問 # 32
Does this run on the VA?
Solution: Active Directory connector
- A. No
- B. Yes
正解：B
解説：
Yes, the Active Directory connector can run on the Virtual Appliance (VA). The VA is responsible for hosting connectors that communicate with various target systems, including Active Directory. The connector establishes the communication between IdentityNow and the target Active Directory instance for operations such as provisioning, deprovisioning, and account synchronization. The VA acts as the bridge between IdentityNow's cloud service and the on-premises AD environment, enabling secure communication through the connector.
Reference:
SailPoint IdentityNow Active Directory Connector Configuration Guide.
SailPoint IdentityNow Virtual Appliance Architecture and Setup Documentation.
質問 # 33
When an engineer goes to Global > System Settings and clicks on System Notifications, the following page opens:
What email notifications are enabled if the engineer selects Sources?
Solution: A notification is immediately sent after successful
- A. Yes
- B. No
正解：B
解説：
In SailPoint IdentityNow, email notifications related to source events (such as successful connections or other operational states) are not automatically sent immediately after a successful source connection. The system focuses on error conditions or alerts based on source status changes or failures. While successful source operations may be logged, notifications are not configured by default to trigger upon every successful action.
Key Reference from SailPoint Documentation:
Source Event Notifications: SailPoint's notifications for source-related events primarily focus on error handling rather than successful operations, which are generally logged for reference but do not trigger immediate notifications.
質問 # 34
An engineer needs to troubleshoot the following issue:
Incomplete Identities on authoritative source
Is this a reasonable action for the engineer to take?
Solution: Download the identity Exceptions report from the identity profile page.
- A. No
- B. Yes
正解：B
解説：
Yes, downloading the Identity Exceptions report from the identity profile page is a reasonable and recommended action when troubleshooting incomplete identities on an authoritative source. This report provides detailed information about any issues or exceptions encountered during identity aggregation, such as missing required attributes or mapping errors. Analyzing this report can help identify the root cause of incomplete identity records and assist in resolving those issues.
Reference:
SailPoint IdentityNow Identity Profile Configuration and Troubleshooting Guide.
SailPoint IdentityNow Exception Handling and Reporting Documentation.
質問 # 35
An IdentityNow engineer has set up an access profile for an application. The access profile allows for users to request access, and for a user's manager to approve or deny access.
After a recent staff meeting, management has expressed that they want to remove any approval requirements for this application.
Is management's request possible in IdentityNow. and. if so. are these the recommended steps the engineer should take to meet their new requirement?
Solution: It is possible. Delete the certification campaign associated with this application.
- A. Yes
- B. No
正解：B
解説：
No, deleting the certification campaign associated with the application is not the correct step to remove approval requirements for an access request. Certification campaigns are related to periodic reviews of access, not the approval workflow for access requests. To remove the manager approval requirement, changes should be made to the access profile or the associated workflow, not the certification campaign.
Key Reference from SailPoint Documentation:
Certification Campaigns: Certification campaigns are used for access reviews and do not control approval workflows for access requests.
質問 # 36
Is the following true about custom connectors in IdentityNow?
Solution: Custom connector are developed and compiled inside identityNow.
- A. Yes
- B. No
正解：B
解説：
No, custom connectors are not developed and compiled inside IdentityNow. Custom connectors are typically developed outside of the IdentityNow platform using a development environment and then tested and packaged before being uploaded to the platform. These connectors can be developed using tools provided by SailPoint, but the actual development process occurs externally, not directly within the IdentityNow environment.
Key Reference from SailPoint Documentation:
Custom Connector Development: Custom connectors are developed outside of the IdentityNow platform and then integrated into it for use.
質問 # 37
Is this an item that an IdentityNow engineer should configure when implementing a source that uses a JDBC connector?
Solution: Use a query select statement with a clause to match the incoming account to an existing account for the Single Account SQL Query configuration item
- A. No
- B. Yes
正解：B
解説：
Yes, using a query select statement with a clause to match the incoming account to an existing account is a key configuration for the Single Account SQL Query in a JDBC connector. This query is used to fetch specific account details from the database and must be written in such a way that it uniquely identifies each account, ensuring accurate correlation between the data in the source and the identities in IdentityNow. Properly configuring this SQL query ensures the right accounts are matched and managed.
Reference:
SailPoint IdentityNow JDBC Connector Single Account Query Configuration Guide.
SailPoint IdentityNow SQL Query Best Practices Documentation.
質問 # 38
Is this an item that an IdentityNow engineer should configure when implementing a source that uses a JDBC connector?
Solution: Define an account schema by using 'Discover Schema'' or by manually configuring the schema attributes.
- A. No
- B. Yes
正解：B
解説：
Yes, defining an account schema is an essential step when implementing a JDBC connector. The schema defines the structure of the identity data being pulled from the database, including the attributes that will be mapped to identity profiles in IdentityNow. The schema can be defined either by using the "Discover Schema" option, which automatically identifies available attributes, or by manually configuring the schema attributes if specific custom mappings are required.
Reference:
SailPoint IdentityNow JDBC Connector Schema Configuration Guide.
SailPoint IdentityNow Source Schema Discovery Documentation.
質問 # 39
......
SailPoint SailPoint-Certified-IdentityNow-Engineerリアルな問題と知能問題集：https://jp.fast2test.com/SailPoint-Certified-IdentityNow-Engineer-premium-file.html