Salesforce Certified Platform Identity and Access Management Architect Practice Test 36
Question 350
An architecture board reviews a proposed Salesforce integration. Context: An integration logs full Authorization headers to simplify debugging of API failures. Finding: Archived logs retain usable bearer tokens after normal application traffic has ended. Which decision best resolves the concern?
- Bind login initiation to the callback using state and appropriate PKCE or anti-forgery validation.
- Set issuer, subject, audience, expiry and signature according to the registered target authorization server.
- Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
- Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.
Explanation
Correct Answer
C:Best. The most direct action is to redact authentication headers and retain only safe correlation data with controlled diagnostic access. It is supported by the specific finding that Archived logs retain usable bearer tokens after normal application traffic has ended. The expected acceptance evidence is: Engineers can investigate failed requests without retaining secrets in permanent logs.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
Question 351
A design workshop describes this environment: An integration logs full Authorization headers to simplify debugging of API failures. Which concrete observation should be documented as the most decisive issue?
- The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.
- An attacker may trick a browser into completing an unrelated authorization transaction.
- Archived logs retain usable bearer tokens after normal application traffic has ended.
- Tokens can be stolen from backups and used until expiry even if a password is changed.
Explanation
Correct Answer
C:Best. The decisive observation is: Archived logs retain usable bearer tokens after normal application traffic has ended. This is why the design response should be: Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner wants users to revoke a connected app's access without changing their Salesforce password. Its relevant condition is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Archived logs retain usable bearer tokens after normal application traffic has ended.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Archived logs retain usable bearer tokens after normal application traffic has ended.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Archived logs retain usable bearer tokens after normal application traffic has ended.
Question 352
An architect must create an acceptance test after choosing: Redact authentication headers and retain only safe correlation data with controlled diagnostic access. For the situation An integration logs full Authorization headers to simplify debugging of API failures. Which result most directly proves success?
- Engineers can investigate failed requests without retaining secrets in permanent logs.
- All identified app access paths are closed and follow-up events confirm containment.
- The token endpoint issues access only for the intended Salesforce org and preauthorized subject.
- The application renews access only for current approved users and destroys tokens at session termination.
Explanation
Correct Answer
A:Best. The verification target is: Engineers can investigate failed requests without retaining secrets in permanent logs. It tests whether the chosen approach—Redact authentication headers and retain only safe correlation data with controlled diagnostic access.—actually resolves the specific finding: Archived logs retain usable bearer tokens after normal application traffic has ended.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security response team revokes a malicious connected app but sees continued API activity afterward. Its relevant condition is: The org has not confirmed whether tokens and application sessions were actually invalidated. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Engineers can investigate failed requests without retaining secrets in permanent logs.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Engineers can investigate failed requests without retaining secrets in permanent logs.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: Engineers can investigate failed requests without retaining secrets in permanent logs.
Question 353
An incident scenario concerns this architecture: An integration logs full Authorization headers to simplify debugging of API failures. The team has discovered: Archived logs retain usable bearer tokens after normal application traffic has ended. Which project risk requires explicit mitigation?
- One copied JavaScript bundle exposes the application credential for all customers.
- Long-lived bearer tokens become a direct route to CRM API data without password verification.
- A person with log-view permission can replay tokens to access Salesforce records.
- OAuth login CSRF links a victim session to an attacker's authorization result.
Explanation
Correct Answer
C:Best. The most direct failure is: A person with log-view permission can replay tokens to access Salesforce records. It is a consequence of the documented condition: Archived logs retain usable bearer tokens after normal application traffic has ended. A mitigation is: Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: A person with log-view permission can replay tokens to access Salesforce records.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: A person with log-view permission can replay tokens to access Salesforce records.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: Archived logs retain usable bearer tokens after normal application traffic has ended. The direct answer here is: A person with log-view permission can replay tokens to access Salesforce records.
Question 354
An architecture board reviews a proposed Salesforce integration. Context: A security response team revokes a malicious connected app but sees continued API activity afterward. Finding: The org has not confirmed whether tokens and application sessions were actually invalidated. Which decision best resolves the concern?
- Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
- Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
- Set issuer, subject, audience, expiry and signature according to the registered target authorization server.
- Bind login initiation to the callback using state and appropriate PKCE or anti-forgery validation.
Explanation
Correct Answer
A:Best. The most direct action is to revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events. It is supported by the specific finding that the org has not confirmed whether tokens and application sessions were actually invalidated. The expected acceptance evidence is: All identified app access paths are closed and follow-up events confirm containment.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
Question 355
A design workshop describes this environment: A security response team revokes a malicious connected app but sees continued API activity afterward. Which concrete observation should be documented as the most decisive issue?
- The org has not confirmed whether tokens and application sessions were actually invalidated.
- Archived logs retain usable bearer tokens after normal application traffic has ended.
- Anyone loading the page can inspect the embedded secret and use it from another device.
- The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.
Explanation
Correct Answer
A:Best. The decisive observation is: The org has not confirmed whether tokens and application sessions were actually invalidated. This is why the design response should be: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: The org has not confirmed whether tokens and application sessions were actually invalidated.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: The org has not confirmed whether tokens and application sessions were actually invalidated.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: The org has not confirmed whether tokens and application sessions were actually invalidated.
Question 356
An architect must create an acceptance test after choosing: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events. For the situation A security response team revokes a malicious connected app but sees continued API activity afterward. Which result most directly proves success?
- The token endpoint issues access only for the intended Salesforce org and preauthorized subject.
- All identified app access paths are closed and follow-up events confirm containment.
- Engineers can investigate failed requests without retaining secrets in permanent logs.
- Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.
Explanation
Correct Answer
B:Best. The verification target is: All identified app access paths are closed and follow-up events confirm containment. It tests whether the chosen approach—Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.—actually resolves the specific finding: The org has not confirmed whether tokens and application sessions were actually invalidated.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: All identified app access paths are closed and follow-up events confirm containment.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: All identified app access paths are closed and follow-up events confirm containment.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: All identified app access paths are closed and follow-up events confirm containment.
Question 357
An incident scenario concerns this architecture: A security response team revokes a malicious connected app but sees continued API activity afterward. The team has discovered: The org has not confirmed whether tokens and application sessions were actually invalidated. Which project risk requires explicit mitigation?
- A person with log-view permission can replay tokens to access Salesforce records.
- Policy changes block new consent while previously issued bearer tokens continue to work.
- OAuth login CSRF links a victim session to an attacker's authorization result.
- One copied JavaScript bundle exposes the application credential for all customers.
Explanation
Correct Answer
B:Best. The most direct failure is: Policy changes block new consent while previously issued bearer tokens continue to work. It is a consequence of the documented condition: The org has not confirmed whether tokens and application sessions were actually invalidated. A mitigation is: Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Policy changes block new consent while previously issued bearer tokens continue to work.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Policy changes block new consent while previously issued bearer tokens continue to work.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The org has not confirmed whether tokens and application sessions were actually invalidated. The direct answer here is: Policy changes block new consent while previously issued bearer tokens continue to work.
Question 358
Salesforce and its partners face the following situation: A company wants employees to use their Salesforce identity to sign into an external procurement portal. The integration review notes: The portal accepts SAML assertions issued by a trusted identity provider. Which architectural step should take priority?
- Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
- Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
- Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
- Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
Explanation
Correct Answer
D:Best. The most direct action is to enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider. It is supported by the specific finding that the portal accepts SAML assertions issued by a trusted identity provider. The expected acceptance evidence is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Its relevant condition is: User subject identifiers and service-provider audience settings differ from the old federation provider. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. Its relevant condition is: Each service has its own audience, service-provider metadata and trust configuration. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
Question 359
An implementation team investigates this scenario: A company wants employees to use their Salesforce identity to sign into an external procurement portal. Which finding would most directly justify a change to the integration architecture?
- The relying party still trusts an old Salesforce IdP signing certificate.
- The portal accepts SAML assertions issued by a trusted identity provider.
- The dashboard can validate signed ID tokens and maintain its own app-specific session.
- The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
Explanation
Correct Answer
B:Best. The decisive observation is: The portal accepts SAML assertions issued by a trusted identity provider. This is why the design response should be: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Its relevant condition is: The relying party still trusts an old Salesforce IdP signing certificate. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: The portal accepts SAML assertions issued by a trusted identity provider.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: The portal accepts SAML assertions issued by a trusted identity provider.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Its relevant condition is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: The portal accepts SAML assertions issued by a trusted identity provider.
Question 360
A solution review asks whether this control is effective: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider. The business setting is: A company wants employees to use their Salesforce identity to sign into an external procurement portal. What should a demonstrable successful outcome be?
- The mobile application receives only necessary authenticated identity data and access permissions.
- The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- Unapproved retired relying parties can no longer request valid identity assertions.
Explanation
Correct Answer
C:Best. The verification target is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions. It tests whether the chosen approach—Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.—actually resolves the specific finding: The portal accepts SAML assertions issued by a trusted identity provider.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Its relevant condition is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security review discovers an unused Salesforce identity-provider service-provider registration. Its relevant condition is: The external application's contract ended but the trusted audience remains in configuration. The present case instead turns on: The portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.