Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam ARC-101 Topic 11 Question 31 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 31
Topic #: 11
[All ARC-101 Questions]

A healthcare services company maintains a Patient Prescriptions System that has 50+

million records in a secure database. Their customer base and data set growing rapidly. They want to make sure that the following policies are enforced:

1. Identifiable patient prescriptions must exist only in their secure system's databaseand

encrypted at rest.

2. Identifiable patient prescriptions must be made available only to people explicit authorized in

the Patient Prescriptions System assigned nurses anddoctors, patient, and people explicitly the

patient may authorize.

3. Must be available only to verified and pre-approved people or legal entities.

To enable this, the company provides the following capabilities:

1. One-time use identity tokens for patients, nurses, doctors, and other people that expire within

a few minutes.

2. Certificates for legal entities.

. RESTful services.

The company has a Salesforce Community Cloud portal for patients, nurses, doctors, and other authorized people. A limited number of employees analyze de identified data in Einstein

Analytics.

Which two capabilities should the integration architect require for the Community Cloud portal

and Einstein Analytics?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Contribute your Thoughts:

Ronny
3 months ago
I'm with the others on C and D. Can't go wrong with those options. Although, I do have to wonder - what's the deal with these one-time use identity tokens? Sounds like a real pain to keep track of!
upvoted 0 times
Minna
2 months ago
D) Encryption in transit and at rest
upvoted 0 times
...
Krystina
2 months ago
C) Callouts to RESTful services
upvoted 0 times
...
...
Reynalda
3 months ago
Haha, I bet the person who wrote this question is a real stickler for security. Probably keeps their own medical records under lock and key! Anyway, I'm saying C and D.
upvoted 0 times
Billi
2 months ago
Definitely, better safe than sorry when it comes to protecting patient prescriptions. C and D it is.
upvoted 0 times
...
Michell
2 months ago
Yeah, we can't be too careful with sensitive information like medical records. C and D cover all the bases.
upvoted 0 times
...
Pura
2 months ago
I agree, security is no joke when it comes to patient data. C and D seem like the best options.
upvoted 0 times
...
...
Bea
3 months ago
I think it could be useful for ensuring secure access to the system.
upvoted 0 times
...
Adelle
3 months ago
C and D for sure. The RESTful services and encryption requirements are spelled out in the question. Gotta love these multiple-choice exams - just need to read carefully!
upvoted 0 times
...
Jules
3 months ago
I'm not sure about storing identity token data, though. Is that really necessary?
upvoted 0 times
...
Tasia
3 months ago
Agreed, it would help in connecting different systems smoothly.
upvoted 0 times
...
Bok
3 months ago
I'm going with B and D. Bulk load for Einstein Analytics seems important for handling the large and growing dataset, and encryption is a no-brainer for this kind of sensitive information.
upvoted 0 times
Mirta
2 months ago
Bulk load for Einstein Analytics and encryption are definitely key for this kind of sensitive data.
upvoted 0 times
...
Louisa
3 months ago
That's a good choice. Bulk load will definitely help with handling the large dataset, and encryption is crucial for protecting sensitive information.
upvoted 0 times
...
Venita
3 months ago
D) Encryption in transit and at rest
upvoted 0 times
...
Gabriele
3 months ago
B) Bulk load for Einstein Analytics
upvoted 0 times
...
Mirta
3 months ago
I agree, B and D are crucial for handling the large dataset and ensuring data security.
upvoted 0 times
...
...
Viola
4 months ago
I also believe callouts to RESTful services are important for seamless integration.
upvoted 0 times
...
Shaquana
4 months ago
I think the correct answers are C and D. The question clearly states that the company provides RESTful services, so the integration architect should require callouts to those services. Additionally, with the sensitive patient data, encryption in transit and at rest is essential.
upvoted 0 times
...
Slyvia
4 months ago
Yes, that's crucial to ensure patient data is protected.
upvoted 0 times
...
Bea
4 months ago
I think we need encryption in transit and at rest for security.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77