What can you bundle using Content Packages?
33 comments · newest first
SH
Shawn
11 months ago
Option C sounds more like archiving than packaging.
SA
Sabrina
12 months ago
Surprised to see both development and content can be bundled!
FR
France
12 months ago
I thought it was just for web content artifacts?
TE
Tegan
1 year ago
Totally agree, that's a key feature!
HA
Hana
1 year ago
You can bundle development and content artifacts into a package.
LE
Lenora
1 year ago
I feel like the answer is A, bundling everything into a deployable unit, but I might be mixing it up with another topic we covered.
RO
Rossana
1 year ago
I vaguely recall something about optimizing storage with archives, which sounds like option C. But I can't remember if that's what Content Packages are really for.
TA
Tamar
1 year ago
I remember practicing a similar question where we discussed web content artifacts specifically. That might be option B, but I feel like there's more to it.
BR
Britt
1 year ago
I think we can bundle development and content artifacts into a single deployable unit, but I'm not entirely sure if that's the main focus of Content Packages.
ID
Idella
1 year ago
The key here is that Content Packages allow you to bundle everything together, not just web content artifacts. I'm confident A is the right answer.
LA
Laura
1 year ago
I'm a bit confused by the question. Is it asking what can be bundled, or what the purpose of Content Packages is? I'll have to read it more closely.
AL
Alita
1 year ago
A for sure. Content Packages are all about packaging up everything you need for deployment, including both code and content.
LA
Lang
1 year ago
Hmm, I'm not too sure about this one. I'll have to think it through carefully. Maybe I should review the content on Content Packages again.
SE
Selma
1 year ago
I think the answer is A. Content Packages allow you to bundle development and content artifacts into a single deployable unit.
IN
Inocencia
1 year ago
I'm feeling pretty confident about this one. Based on the information provided, I believe the management route will be used regardless of the TMM interface status.
AL
Aleta
1 year ago
Hmm, I'm a bit unsure about this one. The options seem similar, but I know there are specific responsibilities for each of these roles. Let me think it through step-by-step.
AI
Aileen
2 years ago
A for sure! Who needs optimized storage when you can have one convenient package to rule them all? Efficiency is key!
EI
Eileen
2 years ago
Hmm, I was leaning towards C at first, but A does sound like the best choice to streamline the whole process. No need to archive everything separately.
NO
Noah
2 years ago
I agree, bundling everything together does seem like the most efficient option.
DE
Derick
2 years ago
A) Development and content artifacts to a single deployable unit (package)
MA
Mattie
2 years ago
Option B seems too limited. I'd go with A to get the full benefits of packaging both development and content pieces together.
ST
Stefania
2 years ago
Yeah, it's a more efficient way to handle both development and content pieces.
GE
Georgiann
2 years ago
I think having everything in one package simplifies the process.
KI
Kirk
2 years ago
It definitely makes it easier to manage and deploy everything as one unit.
TA
Tamera
2 years ago
I agree, bundling development and content artifacts together is more beneficial.
GE
Georgeanna
2 years ago
I think option A is the correct answer. It makes sense to bundle development and content artifacts into a single deployable unit for easier management and deployment.
KE
Keneth
2 years ago
I see your point, bundling everything into a single deployable unit does seem like the best option.
AL
Albina
2 years ago
I prefer option A as well, it just makes the most sense for organization.
VI
Vi
2 years ago
I think option B is also a good choice, bundling web content artifacts can be helpful.
AP
Apolonia
2 years ago
I agree, bundling development and content artifacts together is more efficient.
AR
Armanda
2 years ago
I believe option C is also a valid choice, as it mentions optimizing storage.
MI
Minna
2 years ago
I agree with Claribel, option A makes sense for bundling different types of artifacts.
CL
Claribel
2 years ago
I think you can bundle development and content artifacts using Content Packages.