Pass the SailPoint Identity Security Engineer IdentityNow-Engineer Questions and answers with ValidTests

Not all customers are restricted to a maximum of one non-production tenant. The number of non-production tenants that a customer can have depends on their specific licensing agreement with SailPoint. Some customers may be allowed multiple non-production tenants for various purposes like testing, development, and staging.

Key Reference from SailPoint Documentation:

Tenant Provisioning Guidelines: SailPoint provides flexibility in the number of non-production tenants based on customer agreements, allowing for multiple environments when needed.

Yes, validating the email template (e.g., Certification Due) is a best practice before the campaign preview is generated. Communication during a certification campaign is key to ensuring that managers are aware of their tasks and deadlines. Validating the email templates helps ensure that the messaging is clear, correct, and aligned with the campaign's objectives. It also ensures that any necessary details, such as deadlines, instructions, and links to the certification tasks, are properly included.

Proper validation of email templates helps avoid communication issues that could delay or negatively impact the campaign's success.

References:

SailPoint IdentityNow Certification Campaign Email Templates Guide.

SailPoint IdentityNow Best Practices for Campaign Communication.

No, an access profile does not directly reference roles to provide access. Instead, access profiles are collections of entitlements or permissions that are bundled together to simplify access provisioning. Access profiles can be associated with roles, but they do not reference roles directly. Roles in IdentityNow define broader sets of permissions, which may include access profiles, but access profiles themselves are not tied directly to roles.

References:

SailPoint IdentityNow Access Profiles Documentation.

SailPoint IdentityNow Roles and Access Profiles Configuration Guide.

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.

References:

SailPoint IdentityNow SCIM 2.0 Connector Guide.

SailPoint IdentityNow Connector Overview Documentation.

The virtual appliance (VA) private key is not stored in both the IdentityNow tenant and the VA. The VA private key, which is critical for secure communications, is stored only on the Virtual Appliance (VA) itself. It is used to authenticate and encrypt communications between the VA and the IdentityNow tenant. Storing such sensitive information in the IdentityNow tenant would violate best practices for key management and security.

Instead, the IdentityNow tenant only holds the public key or a reference to the key to facilitate secure exchanges with the VA. The private key remains secured locally within the VA, protecting it from potential security vulnerabilities associated with external storage.

References:

SailPoint IdentityNow Virtual Appliance Architecture Guide.

SailPoint IdentityNow Security and Encryption Documentation.

The use case describes a user logging into IdentityNow via an external identity provider’s login, where information is exchanged via federation. This correctly aligns with the concept of passthrough authentication.

Passthrough authentication often uses protocols like SAML (Security Assertion Markup Language) or OAuth for federation. In this case, the identity provider (IdP) handles the authentication and then passes the necessary authentication tokens or assertions back to SailPoint IdentityNow, granting the user access without directly requiring their password to be stored or authenticated by IdentityNow. This is a typical use case of federation and passthrough authentication.

References:

SailPoint IdentityNow Documentation on SAML and OAuth Federation.

SailPoint IdentityNow Federation and Passthrough Authentication Configuration Guides.

Yes, the Web Services connector in SailPoint IdentityNow supports Basic Authentication. Basic Authentication is a standard method for securing API requests by sending credentials (username and password) encoded in the HTTP headers. This is a common practice for authenticating web service requests, and the Web Services connector in IdentityNow supports it along with other authentication methods like OAuth.

References:

SailPoint IdentityNow Web Services Connector Configuration Guide.

SailPoint IdentityNow Connector Authentication Methods Documentation.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. As part of SailPoint’s multi-tenant SaaS platform, updates are managed and controlled by SailPoint and are pushed out automatically to all tenants. Administrators do not have the ability to schedule or defer updates, as this ensures all customers are running on the latest and most secure version of the software.

References:

SailPoint IdentityNow SaaS Release and Update Policy.

SailPoint IdentityNow Multi-Tenant Environment Overview.

No, verifying that the VA is configured for automatic updates by setting autoupdate=true in the config.yaml file is not directly related to troubleshooting a failed status on the VA. While keeping the VA updated is important for long-term stability and functionality, the configuration for automatic updates does not resolve immediate connection or service failure issues. The troubleshooting focus should be on network connectivity, service status, and log reviews.

Key Reference from SailPoint Documentation:

VA Autoupdate Configuration: Configuring the VA for automatic updates is a best practice for maintaining up-to-date software but is not a direct troubleshooting step for addressing an immediate VA failure.

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.

References:

SailPoint IdentityNow OpenLDAP Connector Guide.

SailPoint IdentityNow SCIM 2.0 Connector Documentation.