SailPoint IdentityNow-Engineer Practice Exam Questions & Answers

No, the search syntax @accounts( source.name:'AD' AND disabled:true ) is incorrect for SailPoint IdentityNow because the attribute disabled may not be universally recognized or applicable for all sources in the system. Using the state:'disabled' condition (as in previous correct answers) is a more reliable and system-compliant approach to find disabled accounts.

Key Reference from SailPoint Documentation:

Standard Account State Search: The correct search syntax involves using state:'disabled' instead of disabled:true for querying disabled accounts.

The search syntax @accounts( source.name:'AD' AND disabled:false ) is not correct for finding disabled AD accounts. This query would return accounts that are not disabled because it is filtering for disabled:false. To find disabled accounts, the filter should specify disabled:true.

Key Reference from SailPoint Documentation:

Search Syntax for Disabled Accounts: To search for disabled accounts, the condition should check for disabled:true.

Yes, this statement is correct. When setting up a Virtual Appliance (VA) cluster, SailPoint does indeed create an asymmetric key pair based on a user-provided passphrase. This key pair is used for secure communication between the Virtual Appliance and the IdentityNow tenant. The asymmetric encryption model uses a public-private key pair where the private key is stored securely within the VA, and the public key is shared with the IdentityNow tenant to establish a secure, encrypted communication channel. This setup ensures that data exchanged between the VA and the IdentityNow tenant remains protected.

SailPoint IdentityNow Virtual Appliance Security Guide.

SailPoint IdentityNow Asymmetric Encryption and Key Management Documentation.

Yes, the fact that the disaster recovery (DR) VAs are not being utilized until a disaster recovery event occurs is a disadvantage. In this strategy, the DR VAs remain idle, leading to underutilization of resources. These VAs could otherwise handle workloads during normal operations to improve efficiency, distribute load, or reduce latency, especially if they are geographically closer to specific target systems. Relying on DR VAs only during failover scenarios limits their potential to optimize performance and balance loads in day-to-day operations.

SailPoint IdentityNow Virtual Appliance Clustering and Disaster Recovery Documentation.

SailPoint IdentityNow High Availability and DR Strategies.

Yes, reviewing the All Source Activity report available in Search is a reasonable action when troubleshooting incomplete identities. This report provides an overview of activity related to source systems, including account aggregations, transformations, and data flow from the source to IdentityNow. By reviewing this report, engineers can identify potential issues such as failed aggregations, data errors, or problems with source connectivity that might be causing incomplete identities.

SailPoint IdentityNow Source Activity Reports Documentation.

SailPoint IdentityNow Troubleshooting Aggregation and Source Issues Guide.

Yes, SailPoint IdentityNow's versioned APIs are fully supported. SailPoint uses versioning in their APIs to ensure backward compatibility, allowing clients to continue using older API versions while newer versions are introduced with additional features and improvements. Versioning helps maintain stability for applications that depend on the APIs.

Key Reference from SailPoint Documentation:

API Versioning: SailPoint IdentityNow provides support for versioned APIs, allowing developers to choose specific versions of the API, which are fully maintained and supported, to prevent breaking changes in integrations.

In this scenario, the Virtual Appliances (VAs) should not reside in the DMZ (B), which is typically used for hosting services that need to be exposed to both internal and external networks, like web servers or email gateways. However, VAs require more direct and secure access to internal resources like Active Directory and databases. The VA needs to reside where it has secure and reliable connectivity to internal resources like Active Directory and database servers, which would be in the internal network.

Key Reference from SailPoint Documentation:

VA Placement Guidance: Virtual Appliances are placed within the internal network, where they can securely connect to Active Directory, databases, and other internal applications for synchronization and provisioning tasks.