An organization runs analytics tasks in a shared environment. They notice that sensitive information remains in storage after tasks finish. They would like to ensure these tasks carry no ongoing state. Which approach is recommended?
Generate credentials that expire after tasks conclude
Use a shared credential across multiple tasks
Avoid encrypting memory segments for computational efficiency
Embed sensitive data within the configuration for convenience
Using credentials that expire when tasks finish helps avoid leftover data. A single credential for all tasks offers broad access, which is risky. Embedding sensitive data in configurations can expose it to unintended viewers, and omitting encryption makes stored data easier to retrieve without authorization.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why do credentials that expire after tasks finish ensure data security?
Open an interactive chat with Bash
What risks are associated with using a shared credential across multiple tasks?
Open an interactive chat with Bash
Why is embedding sensitive data within a configuration considered insecure?